Azure One-click deployment using ARM Template for new Postgres DB does not work

### Version Information

Server Version: 2.33.0

### Environment

Azure Cloud

### What is the current behaviour?

Using the One-click deployment for a new Postgres server on Azure at https://hasura.io/docs/latest/deployment/deployment-guides/azure-container-instances-postgres/ creates the containers and starts them, however the hasura-graphql-engine container appears to keep restarting and so Azure shuts it off:

The Hasura Console is also inaccessible at my FQDN domain.

### What is the expected behaviour?

The container should maintain being up and the Hasura Console should be accessible from the FQDN.

### How to reproduce the issue?

1. Go to https://hasura.io/docs/latest/deployment/deployment-guides/azure-container-instances-postgres/
2. Click Deploy to Azure with new Postgres server
3. Fill out details and create
4. Go to the output FQDN domain and it doesn't load the hasura console.

### Screenshots or Screencast

### Please provide any traces or logs that could help here.

The container doesn't appear to have any logs at all...

### Any possible solutions/workarounds you're aware of?

Start with the Azure deployment guide and the ARM template used by its “Deploy to Azure” flow, then reproduce the restart with a new PostgreSQL server and inspect the generated container settings. Done means the Hasura GraphQL Engine container stays running and the Hasura Console loads at the output FQDN.

Written by the indexing model from the issue text.