feat(gallery): add ha-container-apps-multiregion scenario

[petender]

New Template Registration

Field	Value
Scenario	ha-container-apps-multiregion
Repo	petender/tdd-azd-ha-container-apps-multiregion
Tags	az-204,az-305,msft,aca,acr,frontdoor,keyvault,vnets,virtualmachine,loganalytics,dotnet
Sample App	Yes
Demo Guide	Yes
Contributor	@petender

Tag Validation

All tags validated against src/data/tags.tsx TagType union: ✅ PASSED

Deployment

gh repo clone petender/tdd-azd-ha-container-apps-multiregion cd tdd-azd-ha-container-apps-multiregion azd init azd up

[rob-foulkrod]

While validating this template, I found that the primary region is configurable through the AZD/Azure location, but the secondary region is hardcoded in infra/main.bicepparam:

param location = readEnvironmentVariable('AZURE_LOCATION', 'eastus2')
param secondaryLocation = 'westus3'

This makes validation and fallback-region selection difficult. For example:

• Deploying with primary westus3 causes ACR geo-replication to target the same region as the registry home region, which fails.
• Deploying with primary westus and secondary westus3 avoids that ACR issue, but failed because westus did not support the required availability-zone configuration.
• The intended pair appears to be eastus2 + westus3, but if eastus2 has subscription quota/capacity constraints, there is no clean way to choose another compatible primary/secondary pair without editing the template.

Could you make secondaryLocation configurable through AZD input/env config, or explicitly document that this template must be deployed with primary eastus2 and secondary westus3?