chore: Add AZD Template Validation Workflow (Scheduled & On-Demand) and Refactor Azure Deployment Pipeline

[VishalS-Microsoft]

Purpose

This pull request restructures the GitHub Actions workflows related to Azure template validation and deployment. The main change is the separation of template validation and deployment into two distinct workflows: one for scheduled template validation and another for manual deployment. The validation workflow is now more robust and automated, while the deployment workflow is streamlined for production use.

Workflow Restructuring:

• Created a new workflow .github/workflows/azd-template-validation.yml that runs template validation on a schedule (every Thursday) and on manual trigger, using microsoft/template-validation-action with environment variables and secrets for Azure authentication.
• Refactored .github/workflows/azure-dev.yaml to focus solely on deployment, renaming it to "Azure Dev Deploy", removing template validation steps, and updating the deployment steps to use azd and azure/login actions for provisioning and deploying resources.

Security and Permissions Updates:

• Adjusted permissions in both workflows, ensuring only necessary permissions are granted for each workflow’s scope. [1] [2]

Environment and Variable Handling:

• Improved handling of environment variables and secrets for both validation and deployment, including the use of GitHub Actions variables and Azure credentials. [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