Use latest API versions in all modules

[olljanat]

Overview/Summary

Cherry-picked API version updates from #245 which have not been yet updated since that one was created.

Related to #247

This PR fixes/adds/changes/removes

One example of this kind of case Azure/bicep#5581 (comment)

Also fixes location in pipelines being consistently taken from key vault/variable instead of hardcoded in places to eastus

Breaking Changes

• Private DNS Zones vNet linking name made unique to ensure can be used multiple times for vNets with the same names:
  

Testing Evidence

Should be as long as e2e tests pass.

As part of this Pull Request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• 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 tests (if required) Unit - Linting - E2E (End-To-End)
• 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 validate az cloud

[azure-pipelines]

No pipelines are associated with this pull request.

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

/azp run e2e

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[olljanat]

oh, I totally forgot that those Azure Pipelines are not public.
@jtracey93 can you copy pipeline logs/errors from there to here as record?

[jtracey93]

oh, I totally forgot that those Azure Pipelines are not public. @jtracey93 can you copy pipeline logs/errors from there to here as record?

Hey @olljanat, yup just one of those things im afraid due to the way GitHub handles secrets in PRs from Forks.

The errors were mainly vwan DNS Zone related, so nothing you did but something your bigger change forced a run of the entire pipeline and highlighted. I have made some changes in your branch to fix and will re-run the tests:

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

/azp run e2e

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

/azp run e2e

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

/azp run e2e

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jfaurskov]

/azp run ValidateMcCloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jfaurskov]

LGTM, also tested validate in Mooncake with no issues