feat: child modules telemetry check

[ReneHezser]

Description

Child modules should be references with telemetry disabled. A static test checks that and lists the affected resources.

[-] [network/virtual-network] Telemetry should be disabled for referenced modules with dedicated telemetry. 3150.12s (3150.12s|1ms)
     Expected $null or empty, because cross reference modules must be referenced with the enableTelemetry parameter set to false. Found incorrect items: [virtualNetwork_subnets, virtualNetwork_peering_local]., but got @('virtualNetwork_subnets', 'virtualNetwork_peering_local').
     at $incorrectCrossReferences | Should -BeNullOrEmpty -Because ('cross reference modules must be referenced with the enableTelemetry parameter set to false. Found incorrect items: [{0}].' -f ($incorrectCrossReferences -join ', ')), C:\Code\bicep-registry-modules\utilities\pipelines\staticValidation\compliance\module.tests.ps1:1023
     at <ScriptBlock>, C:\Code\bicep-registry-modules\utilities\pipelines\staticValidation\compliance\module.tests.ps1:1023

Depends on Cross referenced Modules

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

[eriqua]

I'd suggest to run the static validation step only on the whole library before merge

[ReneHezser]

Done. No red pipeline is a result of this PR. I've updated all res modules to fulfill the new spec.

[AlexanderSehr]

Hey @ReneHezser, just added one ask as a comment and resolved the rest. Looks legit. 💪

[AlexanderSehr]

Hey @ReneHezser,
I'll review the PR over the weekend.

Edit: Done

[AlexanderSehr]

General comment regarding workflows

To remidiate

• avm.res.network.virtual-network would run if you pull latest upstream. The module is not orhpaned anymore
• avm.res.document-db.database-account failed due to transient error

For Info

• elastic-san/elastic-san fails due to a bug in the If a UDT definition [managedIdentitiesType] exists and supports system-assigned-identities, the template should have an output for its principal ID. test. This is not caused by your changes, but I found it worth pointing out as this was not tracked (- created PR fix: Fixed MSI UDT test to only check for the required output if the imported type is also used by a parameter  #4498)
• azd/apim-api failed due to the module using \n as a line-ending, but your local devise used \r\n. This is already an issue in main and not related to your code. But it's an interesting takeaway - presumably caused by a contributor on Linux/Mac.