fix: avm/ptn/ai-platform/baseline Enforce location when deploying VM with zones

[cecheta]

Description

This fixes the CI build, by deploying the VM with an availability zone into uksouth, as there are no zone restrictions in this location.

Error from pipeline.

  VERBOSE: 08:53:09 - The deployment 'a-p-ap-b-waf-aligned-t1-20240814T0808098316Z' failed with error(s). Showing 2 out of 2 error(s).
  Status Message: The template deployment 'idx4jtu3qkiqg-virtual-machine' is not valid according to the validation procedure. The tracking id is '3498bd14-2fe0-49c5-84d8-d8c5037ee9be'. See inner errors for details. (Code: InvalidTemplateDeployment)
   - The requested VM size for resource 'Following SKUs have failed for Capacity Restrictions: Standard_D2s_v3' is currently not available in location 'westeurope'. Please try another size or deploy to a different location or different zone. See https://aka.ms/azureskunotavailable for details. (Code:SkuNotAvailable)
  Status Message: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details. (Code: DeploymentFailed)
   - The template deployment 'idx4jtu3qkiqg-virtual-machine' is not valid according to the validation procedure. The tracking id is '3498bd14-2fe0-49c5-84d8-d8c5037ee9be'. See inner errors for details. (Code: InvalidTemplateDeployment)
     - The requested VM size for resource 'Following SKUs have failed for Capacity Restrictions: Standard_D2s_v3' is currently not available in location 'westeurope'. Please try another size or deploy to a different location or different zone. See https://aka.ms/azureskunotavailable for details. (Code:SkuNotAvailable)
  CorrelationId: 1c745da8-57c2-47a6-936a-e7b5e22f698d

Also disabling availability zones for max example, so this does not fail either.

Pipeline Reference

Pipeline

Note: I can only run this in my subscription if I hardcode the location in the pipeline to uksouth, as I cannot deploy any VMs into westeurope, which I why this was not caught earlier.

Type of Change

• Update to CI Environment or utilities (Non-module affecting changes)
• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[microsoft-github-policy-service]

Important

If this is a module-related PR, being submitted by the sole owner of the module, the AVM core team must review and approve it (as module owners can't approve their own PRs).

To indicate this PR needs the core team''s attention, apply the "Needs: Core Team 🧞" label!

The core team will only review and approve PRs that have this label applied!

[cecheta]

Moving to #3044