ci: Enhanced deployment workflow with better resource management, cleanup logic

[Vamshi-Microsoft]

Purpose

This pull request significantly refactors the Azure deployment GitHub Actions workflow by introducing dynamic environment and resource group naming, switching to the Azure Developer CLI (azd) for deployment and cleanup, and improving secrets management and output reporting. The changes aim to make deployments more robust, flexible, and suitable for production environments, while also adding automated resource cleanup.

Key changes include:

Deployment workflow modernization:

• Replaces static environment and resource group names with dynamically generated unique names for each workflow run, improving isolation and reducing naming collisions.
• Switches from using repository variables to GitHub secrets for sensitive Azure credentials and sets additional environment variables for deployment consistency.
• Updates the deployment process to use the Azure Developer CLI (azd) for authentication, environment management, and resource provisioning, replacing direct Bicep deployments and custom Python scripts.

Resource management and cleanup:

• Adds a new cleanup job that automatically tears down deployed resources after the workflow completes, using azd down and a fallback resource group deletion step to ensure no orphaned resources remain.

Output and reporting improvements:

• Enhances deployment and cleanup summaries with dynamically populated resource names and Azure Portal links, making it easier to track and verify deployed and deleted resources.

Workflow structure and environment changes:

• Consolidates build and deploy jobs under a production environment, and updates job dependencies and outputs to support the new dynamic naming and cleanup logic. [1] [2]

These improvements make the workflow more secure, maintainable, and production-ready, while also reducing manual intervention for resource cleanup.

Does this introduce a breaking change?

• Yes
• No