ci: Down merge from main to dev-v4

[Dhruvkumar-Microsoft]

Purpose

This pull request makes significant improvements to the GitHub Actions deployment workflows by consolidating OS-specific workflows, enhancing input validation, and modernizing Azure authentication. The changes streamline deployment configuration, increase flexibility for different environments, and improve security by switching to OIDC-based Azure login. The most important changes are grouped below:

Workflow Consolidation and Environment Flexibility

• Removed deploy-windows.yml and merged its functionality into a renamed and enhanced deploy-v2.yml, allowing selection between Windows and Linux runners via a new runner_os input parameter. This enables a single workflow to handle deployments on both platforms, simplifying maintenance and reducing duplication. [1] [2] [3] [4]
• Added logic to deploy-v2.yml to resolve the runner OS based on user input, with validation and clear error messaging for invalid values. [1] [2]

Input Validation and Output Improvements

• Improved input validation in deploy-v2.yml to ensure deployment parameters are correct and outputs are properly set, including the resolved runner OS, Azure location, and other deployment options. [1] [2]
• Updated workflow dispatch and job outputs to propagate validated values to downstream jobs, increasing reliability and clarity in deployments.

Azure Authentication Modernization

• Replaced legacy service principal login with the official azure/login@v2 GitHub Action, leveraging OIDC for improved security and easier credential management in deploy.yml and deploy-waf.yml. [1] [2] [3] [4]
• Added id-token: write permission to deployment workflows to support OIDC authentication. [1] [2] [3]

Workflow Permissions and Environment Settings

• Added environment: production to deployment jobs for better environment tracking and permissions management. [1] [2]
• Cleaned up and standardized permissions and environment configuration across workflows, including removing redundant permissions from orchestrator and validation jobs. [1] [2]

---

These changes collectively modernize the deployment process, increase flexibility for different runner environments, and improve security and maintainability of the CI/CD pipeline.

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