fix: Prevent removal of existing RG tags when deploying GSA

[Kanchan-Microsoft]

Purpose

This pull request improves the clarity and user-friendliness of post-deployment instructions in both Windows and Bash environments, enhances the tagging logic in the infrastructure code, and adds a check for existing teams in the team configuration upload script to prevent duplicate uploads.

Improvements to deployment scripts and user guidance:

• Enhanced the post-deployment instructions in both azure.yaml and azure_custom.yaml for Windows (PowerShell) and POSIX (Bash) environments by adding step-by-step guidance, color-coded output, and clearer messaging for uploading team configurations, indexing sample data, and accessing the deployed frontend application.

Infrastructure enhancements:

• Updated the infra/main.bicep template to merge existing resource group tags with new tags, ensuring all relevant tags are preserved and applied to the resource group.

Backend script improvements:

• Added a check_team_exists function to infra/scripts/upload_team_config.py to verify if a team already exists before attempting to upload its configuration, preventing duplicate uploads and providing informative output when a team is already present.

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