Filter the allowed location to use EastUs2, and avoid deploy issues

[elbruno]

Purpose

• Filter the allowed location to use EastUs2, and avoid deploy issues

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Deploy

azd up

What to Check

Verify that the following are valid

• Deploy works correctly

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

Files not reviewed (1)

• infra/main.bicep: Language not supported

Comments suppressed due to low confidence (2)

README.md:174

• The region name 'EastUS2' is inconsistent with 'East US 2' used elsewhere. It should be renamed to 'East US 2'.

> This application uses the `gpt-4o-mini` model. When choosing which region to deploy to, make sure they're available in that region (i.e. EastUS2). For more information, see the [Azure OpenAI Service documentation](https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/models#standard-deployment-model-availability).

README.md:330

• The region name 'eastus2' is inconsistent with 'East US 2' used elsewhere. It should be renamed to 'East US 2'.

azd env set AZURE_OPENAI_RESOURCE_LOCATION eastus2 # Please check the gpt model availability for more details.