[vwanConnectivity] Refactor to support multi-region hubs

[sebassem]

Overview/Summary

This PR is changing the way Azure Firewall parameters are handled in the module to be per Hub, currently there are common parameters for Azure Firewall that will be applied to every instance in all hubs. Customers may want to customize the policies, dns servers,.tiers,...etc per region per hub.

This PR fixes/adds/changes/removes

1. Closes #750

Breaking Changes

1. Moved the following parameters into the UDT of virtualWanOptionsType to allow for different firewall configuration per hub/region
   • parAzFirewallDnsServers
   • parAzFirewallIntelMode
   • parAzFirewallDnsProxyEnabled
   • parAzFirewallTier
   • parAzFirewallAvailabilityZones

Testing Evidence

As part of this Pull Request I have

• [X] Read the Contribution Guide and ensured this PR is compliant with the guide
• [X] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
• [X] Checked for duplicate Pull Requests
• [X] Associated it with relevant GitHub Issues
• [X] (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
• [X] Ensured my code/branch is up-to-date with the latest changes in the main branch
• [X] 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

[oZakari]

/azp run validateazcloud

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[oZakari]

/azp run validateazcloud

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).