feat: Added Deployment v2 pipeline with Windows and Linux support

[Vamshi-Microsoft]

Purpose

This pull request introduces a new, modular deployment workflow for both Linux and Windows environments, centralizing orchestration and cleanup logic for Azure-based deployments. The changes add new workflow files for deployment and cleanup, improve parameterization and flexibility for deployment jobs, and ensure better reporting and resource management.

New deployment orchestration and job modularization:

• Added .github/workflows/deploy-orchestrator.yml to centralize deployment orchestration, handling Docker build, deployment, end-to-end testing, notifications, and cleanup as separate jobs. This workflow receives parameters from platform-specific workflows and coordinates job execution, improving maintainability and extensibility.
• Introduced .github/workflows/job-cleanup-deployment.yml to encapsulate resource cleanup logic, including optimized Azure resource group deletion, authentication, and job summary reporting. This modular job is called by the orchestrator workflow as needed.

Platform-specific workflow enhancements:

• Added .github/workflows/deploy-linux.yml and .github/workflows/deploy-windows.yml to serve as entry points for Linux and Windows deployments, respectively. These workflows collect user inputs, trigger the orchestrator, and support flexible deployment scenarios (e.g., skipping deployment, enabling WAF/EXP, running tests, and scheduling). [1] [2]

Parameterization and flexibility improvements:

• Both orchestrator and entry-point workflows now support a wide range of inputs (Azure location, resource group, WAF, EXP, Docker build, cleanup, test suite selection, existing webapp URL, and more), allowing for customizable deployment and testing flows. [1] [2] [3] [4]

Reporting and error handling:

• Cleanup job now generates a detailed summary in the GitHub Actions job summary, indicating resource group deletion status and providing guidance on manual cleanup if needed.

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

• I have built and tested the code locally and in a deployed app
• For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
• This is a change for all users of this app. No code or asset is specific to my use case or my organization.

[github-actions]

🎉 This PR is included in version 1.7.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀