fix: Downmerge from dev to dependabotchanges

[Priyanka-Microsoft]

Purpose

• ...
  This pull request introduces a series of improvements and enhancements across the CI/CD workflows, environment configuration, and developer tooling for the project. The main focus is on streamlining Docker build and deployment processes, improving CI pipeline flexibility and robustness, updating environment variable samples, and enhancing developer experience. Below are the most important changes grouped by theme:

CI/CD Pipeline and Workflow Enhancements

• Refactored the Docker build and push workflows to remove legacy registry logic, standardize on the new registry (cwydcontainerreg), and update image tagging conventions (e.g., using latest_waf for the main branch). This simplifies the deployment process and reduces maintenance overhead. [1] [2] [3] [4] [5] [6]
• Improved the main CI workflow (ci.yml) by adding steps to generate unique resource group names and solution suffixes, check and create resource groups as needed, and increase the GPT minimum capacity for quota checks. These changes make deployments more robust and easier to track. [1] [2] [3] [4]
• Updated the extraction of deployment URLs from logs to ensure uniqueness and reliability by sorting, deduplicating, and selecting the first match for both admin and web URLs.
• Added new environment outputs and variables in the CI workflow, including resource group and solution suffix, and ensured these are passed to subsequent jobs and deployment steps. [1] [2] [3]
• Updated the actions/checkout version to v5 in all workflows for improved performance and security. [1] [2] [3] [4]

Environment and Developer Tooling

• Added new sample environment variables to .env.sample for Azure Search columns, logging configuration, and application environment, providing better guidance for local and cloud deployments. [1] [2] [3]
• Upgraded the base image in .devcontainer/Dockerfile to use the bookworm variant and updated installation commands in .devcontainer/setupEnv.sh for more reliable and up-to-date developer environments. [1] [2]

Automation and Code Ownership

• Expanded the list of code owners in .github/CODEOWNERS to include additional maintainers, ensuring better code review coverage.
• Improved the broken links checker workflow to use more efficient actions for detecting changed markdown files and upgraded the link checker version for manual runs.

These changes collectively improve the reliability, maintainability, and developer experience of the project’s CI/CD and local development processes.

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