Multiregion bugfix

[brsteph]

Overview/Summary

This PR is to fix issues identified with deploying networks after the multi-region update and recent product changes. Discovered in: https://dev.azure.com/CSUSolEng/Azure%20Landing%20Zones/_workitems/edit/35833

Core issues are:

• Attempts to peer networks incorrectly - the deployment was trying to peer ID spoke networks incorrectly, and was also trying to peer hubs even when one hub is in use.
• Zonal IPs for Gateway SKUs - A new zone property was needed for zonal gateway public IPs.
• Issues with secondary region DNS proxy configuration on the Firewall.

This PR fixes/adds/changes/removes

1. Adjusted the logic to better limit the parameters used to initiate a secondary region deployment.

Breaking Changes

1. None

Testing Evidence

Confirmation of Gateway Deployment:

Confirmation of single region deployment:

ID Spoke and Peering:

Confirmation of DNS Proxy for Secondary Region:

Testing URLs

The below URLs can be updated where the placeholders are, look for {YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also} & {YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also}, to allow you to test your portal deployment experience.

Please also replace the curly brackets on the placeholders {}

Azure Public

Azure US Gov (Fairfax)

As part of this Pull Request I have

• Checked for duplicate Pull Requests
• Associated it with relevant issues, for tracking and closure.
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Ensured contribution guidance is followed.
• Updated relevant and associated documentation.
• Updated the "What's New?" wiki page (located: /docs/wiki/whats-new.md) (N/A for bugfix)

[brsteph]

@jtracey93 - Updated!