Standardize on parLocation for specifying Azure regions.

[rjygraham]

Renames all instances of parRegion to parLocation in code and documentation to be in alignment with the vast majority of ALZ-Bicep modules and ARM/TF ESLZ.

This PR fixes/adds/changes/removes

1. All occurrences of parRegion renamed to parLocation

Breaking Changes

1. Existing clones of the ALZ-Bicep repository will need to update parRegion to parLocation for deployments of hubNetworking and spokeNetworking module parameter files.

Testing Evidence

hubNetworking

spokeNetworking

As part of this Pull Request I have

• Checked for duplicate Pull Requests
• 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 relevant and associated documentation.

[jtracey93]

Thanks @rjygraham nice work. I think we need to also update the logging and resource group module as they don't use the new standard of parLocation here. They use some thing like parResourceGroupLocation etc. let's make them all the same 👍

Also in the contributing wiki page can we add a new "Standardised Common Parameter" section for things like this and tags etc.

[jtracey93]

Linking to ADO item: https://dev.azure.com/unifiedactiontracker/Solution%20Engineering/_workitems/edit/100633

[rjygraham]

@jtracey93 - due to disparity in China region availability for Log Analytics and Automation Accounts, I believe we'll need to leave the logging module with separate parameters for now: parAutomationAccountRegion and parLogAnalyticsWorkspaceLocation instead of a single parLocation parameter.

[jtracey93]

@jtracey93 Jack Tracey FTE - due to disparity in China region availability for Log Analytics and Automation Accounts, I believe we'll need to leave the logging module with separate parameters for now: parAutomationAccountRegion and parLogAnalyticsWorkspaceLocation instead of a single parLocation parameter.

Lets chat on our sync tomorrow to understand more here.

[jtracey93]

@rjygraham is this good to review again?

With the changes we spoke about yesterday?

[rjygraham]

@jtracey93 yes - all good to review. I just did another merge of main to resolve another conflict that was introduced.

[jtracey93]

/azp run e2e

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

Nice work @rjygraham LGTM 🚢