ALZ bicep modules multi-region guidance

[sebassem]

Overview/Summary

This PR is adding examples and guidance on how to deploy ALZ platform resources into multiple regions. It covers hub and spoke and vwan modules

This PR fixes/adds/changes/removes

Closes #375

Breaking Changes

None

Testing Evidence

This PR only has readme changes

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
• [] (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.
• [X] 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)
• [X] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
• [ ] If relevant, created or updated Code Tours here

[sebassem]

@oZakari @jtracey93 This is a still a WIP but wanted to share an early draft of the hubNetworking multi-region guidance. Please let me know if you have comments/feedback so I can start on the vWan module next.

[sebassem]

This PR is dependent on https://github.com/Azure/ALZ-Bicep/pull/805

[sebassem]

Hey @sebassem, I think the docs are concise and clear. I have made some updates to the hub networking module readme, particularly with switching to East US and West US since they are paired regions. Also, demonstrates that they will need to look out for the regions that do/dont support availability zones to determine which parameter file to use.

I also removed the example parameter files to avoid bloat as I think it should be pretty easy to follow that they just need to change the regions. Let me know if you object though and we can discuss.

Could you please update the East US 2 example output to West US? After that I think it is good to merge as long as good on your end.

Thanks Zach, screenshot has been updated

[oZakari]

/azp run validateazcloud

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).