Improved control of PrivateDnsZones beeing deployed

[picccard]

Overview/Summary

When hubNetworking.parameters.all.json or vwanConnectivity.parameters.all.json contains no Zone for Azure Backup, the module will deploy a zone for the service anyway, aslong as there exists one in the deployment-location.

This PR allows the consumer to skip the Azure-Backup-Zone lookup and only deploy the zones provided in parPrivateDnsZones.

...
"parPrivateDnsZones": {
  "value": [
    "privatelink.blob.core.windows.net",
    "privatelink.file.core.windows.net"
  ]
},
...

This PR fixes/adds/changes/removes

1. Adds a new bool param parPrivateDnsZoneAutoMergeAzureBackupZone in modules privateDnsZone, hubNetworking and vwanConnectivity

Breaking Changes

None, it is optional to make use of this.

Testing Evidence

Setting the flag to false prevents the auto merged zone for azure backup from beeing deployed.

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]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).