fix: add westus3 in replicaRegionPairs

[Shreyas-Microsoft]

Purpose

This pull request makes a small update to the region pairing configuration in the infra/main.bicep file. The main change is the addition of a new region mapping for westus3 to eastus in both the general replica region pairs and the Cosmos DB high-availability region pairs. This ensures that deployments in the westus3 region will have an appropriate paired region for redundancy and high availability.

• Region pairing updates:
  • Added a mapping for westus3 to eastus in the replicaRegionPairs variable to support redundancy for resources deployed in westus3.
  • Added a mapping for westus3 to eastus in the cosmosDbZoneRedundantHaRegionPairs variable to ensure Cosmos DB high-availability deployments in westus3 are paired with eastus.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀