refactor: Updated Foundry Roles name

[AjitPadhi-Microsoft]

Purpose

• This pull request standardizes the naming of a specific Azure role throughout the codebase and documentation, changing all references from "Azure AI User" to "Foundry User". It also updates related comments, messages, and documentation to reflect this new terminology. Additionally, there are minor changes to resource dependency ordering and template formatting to improve clarity and consistency.

Role Naming Standardization:

• All references to the "Azure AI User" role are updated to "Foundry User" in Bicep modules (infra/main.bicep, infra/main_custom.bicep), shell scripts (infra/scripts/run_create_agents_scripts.sh, infra/scripts/run_create_index_scripts.sh), batch files (src/start.cmd), shell scripts (src/start.sh), and documentation (documents/LocalDevelopmentSetup.md). This includes comments, user-facing messages, and role assignment logic. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Infrastructure and Template Updates:

• The infra/main.json template hash is updated, and the formatting of the reactAppLayoutConfig parameter is improved for readability. [1] [2]
• Resource dependency arrays in infra/main.json are reordered for clarity and possibly to ensure correct deployment order. [1] [2]

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