ci: Fixed Pipeline Security vulnerabliity

[Kanchan-Microsoft]

Purpose

This pull request introduces several improvements to the GitHub Actions workflows for deployment and infrastructure automation. The main focus is on enhancing workflow security by explicitly setting permissions, increasing input validation robustness, and modernizing environment and credential handling for Azure deployments. It also removes redundant steps and streamlines the setup of required tools.

The most important changes are:

Security and Permissions

• Explicitly set minimal permissions (contents: read, actions: read) for all major workflow files to follow GitHub Actions best practices and reduce the risk surface.

Input Validation and Robustness

• Introduced a comprehensive input parameter validation step in job-deploy-linux.yml, checking for required values, correct formats, and valid Azure resource IDs. This prevents misconfigured deployments by failing fast with clear error messages.

Azure Environment and Credential Handling

• Updated environment variable usage for Azure credentials and deployment parameters, switching from inline export statements to the more secure and readable env: block in workflow steps.
• Modernized setup of Azure CLI and Azure Developer CLI by removing manual installation commands and using the official Azure/setup-azd@v2 action for better reliability and maintainability.

Workflow Step Improvements

• Improved the deployment summary generation and role assignment steps to use environment variables, making the code more maintainable and less error-prone.
• Updated the Azure template validation action to use a specific commit hash for better reproducibility and security.

These changes collectively improve the reliability, security, and maintainability of the CI/CD pipeline for Azure deployments.

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