fix: Update solutionLocation parameter to use dynamic location value

[Harmanpreet-Microsoft]

Purpose

this is fix to:#1907

This pull request updates the infrastructure deployment configuration to improve flexibility and maintain consistency across environments. The main change is to make the deployment location configurable instead of hardcoding it, and to ensure that the Bicep and generated ARM templates (main.bicep and main.json) are in sync.

Key changes include:

Parameterization and Configuration Improvements

• Changed the solutionLocation parameter in both main.bicep and the generated main.json from a hardcoded value (eastus2) to use the configurable location parameter, allowing deployments to target different Azure regions more easily. [1] [2]

Template Synchronization and Versioning

• Regenerated the infra/main.json ARM template to reflect the updated Bicep source, including changes to the Bicep compiler version and template hashes throughout the file. This ensures the JSON output matches the latest Bicep source and configuration. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31]

• ...

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

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

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information