chore: Down merge from main to dev

[Prajwal-Microsoft]

Purpose

This pull request updates the deployment and notification workflows to improve status tracking and notification details, especially around the cleanup stage. The main changes include passing cleanup results to the notification workflow, updating notification content to include a summary of deployment and cleanup statuses, and refactoring notification logic for clarity. There are also minor documentation improvements.

Workflow and Notification Improvements:

• The send-notification job in .github/workflows/deploy-orchestrator.yml is now triggered after the cleanup-deployment job and receives both deployment and cleanup results as inputs. This ensures notifications accurately reflect the state of both stages. [1] [2]
• The job-send-notification.yml workflow now accepts a cleanup_result input and determines a human-readable cleanup status for use in notifications. [1] [2]
• Notification emails for deployment success, failure, and quota failure now include a status summary table showing both deployment and cleanup results, as well as a configuration label for WAF/EXP settings. Subjects and bodies are more informative and standardized.
• The step for sending a notification about a skipped deployment due to an existing web app URL has been removed, streamlining the workflow.

Documentation Updates:

• The role name in the deployment guide was clarified from "Role Based Access Control" to "Role Based Access Control Admin".
• Added a note to the deployment guide for users of azd version 1.23.9 to set a configuration value to avoid preflight checks.

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

[github-actions]

🎉 This PR is included in version 1.0.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀