Nested deployments should get passed the value for parTelemetryOptOut

[picccard]

Overview/Summary

The orchestrator modules mgDiagSettingsAll.bicep and subPlacementAll.bicep does honor the param parTelemetryOptOut, but every nested deployment they produce does not honor it. Instead they use the default parameter-value. This results in unwanted telemetry as shown below.

This also applies to the module policyAssignmentManagementGroup.bicep, here even more telemetry is generated, as show in the second picture.

This PR fixes/adds/changes/removes

Pass the param parTelemetryOptOut to every nested module in:

1. mgDiagSettingsAll.bicep
2. subPlacementAll.bicep
3. policyAssignmentManagementGroup.bicep

Breaking Changes

None

As part of this Pull Request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues
• (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Updated one or more of the following tests (if required)
  • Unit
  • Linting
  • E2E (End-To-End)
  • ValidateAzCloud (Base validation in Azure Cloud)
  • ValidateMcCloud (Base validation in Azure China Cloud)
• Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
• If relevant, created or updated Code Tours here

[jtracey93]

Thanks @picccard for spotting this and resolving, LGTM. Will test and merge

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).