fix: Adding certificates child resource and updated max test

[hundredacres]

Description

Added certificate child resource, updated the max test to test for it and removed unnecessary deps.

Fixes #3855
Closes #3855

Pipeline Reference

Pipeline

Type of Change

• Update to CI Environment or utilities (Non-module affecting changes)
• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings

[AlexanderSehr]

Hey @hundredacres,
I won't block the PR over it but want to raise one question:
The certificateKeyVaultProperties are technically a property of the certificate child module - and could be part of the certificateObject. However, they're instead currently decleared as a separate parameter.
What I'm wondering is, if it would be better / more intuitive to merge the parameter into the wider certificateObject parameter (that is, merging the two parameters into one), and having line 179 and follwing simply reference the property from this location like

      certificateKeyVaultProperties: !empty(certificateObject.?certificateKeyVaultProperties)
        ? {
            identity: certificateObject!.certificateKeyVaultProperties!.identityResourceId
            keyVaultUrl: certificateObject!.certificateKeyVaultProperties!.keyVaultUrl
          }
        : null

In general it seems a bit confusing that this and other parameters like the certificateValue, certificatePassword, etc. are all duplicated.
Could it be that the child is even the same as the property? If so, it may even be possible to not define the properties in line 175 and following at all, and instead have the child take care of it exclusively.

Just some thoughts. Maybe completely wrong 😄 Just wanted to ask as I got a bit confused over it.

[AlexanderSehr]

Hey @hundredacres,
did you happen to find out anything about it? Do both need to be declared? The PR already looks good as it is as far as I'm concerned. Would just be curious.

[AlexanderSehr]

Suggested change

	}?
	}

Parameter is already (correctly) nullable

[AlexanderSehr]

Hey @hundredacres,
the PR looks pretty much good as is. I added one comment that should be addressed (regarding the nullable), and the other comment you could resolve as it's just a question as I find the resource provider a bit ... unintuitive 😄 But that's obviously not on you.