Add infrastructure automation to configure custom domain and SSL certificates

[tjementum]

Summary & Motivation

Introduce Bicep code to automate the configuration of a Custom Domain and the automatic creation of a valid SSL Certificate for the account-management-api. This process unfolds in three distinct steps:

1. Deploy the container apps environment to retrieve the auto-generated environment URL and the Custom Domain Verification Id.
2. Deploy the container app again to set up the Domain and SSL Certificate, albeit without binding them (as this is not supported in one step; see https://github.com/microsoft/azure-container-apps/tree/main/docs/templates/bicep/managedCertificates).
3. Proceed to bind the SSL certificate to the domain.

The first step will fail when initially setting up custom domains. Bash scripts have been crafted to extract the container app url and Domain Verification ID, providing clear instructions on how to configure CNAME and TXT records to validate domain ownership. Moreover, the procedures for the second and third steps will be executed automatically if needed, streamlining the overall process.

Bash scripts responsible for deploying Bicep code have been updated with enhanced error management.

Update the initialize-azure.sh Bash script, incorporating guidelines on establishing GitHub environments and setting up the DOMAIN_NAME variables.

Simplify the overall deployment structure from GitHub to Azure by adopting a single shared Service Principal. This unified approach caters to the deployment of Bicep infrastructure, the push of container images to ACR, and the deployment of these images across various environments.

Checklist

• I have added a Label to the pull-request
• I have added tests, and done manual regression tests
• I have updated the documentation, if necessary