Add retries for sqlcmd in sqlserver.bicep

[weikanglim]

Problem

sqlcmd (relevant code here) often fails to connect to the newly provisioned database when azd provision runs, with error:

"Database '<>' is not currently available. Please retry this connection later."

Example failures:

• https://github.com/colbylwilliams/dotnet-podcasts/actions/runs/4853091939
• https://github.com/colbylwilliams/dotnet-podcasts/actions/runs/4852275258/jobs/8647818046
• https://github.com/colbylwilliams/dotnet-podcasts/actions/runs/4815873884/jobs/8574964982

Fix

1. We should add retries for failure conditions in the deployment script, and timeout after 3-5 minutes.
2. We should investigate if sqlcmd is logging errors to standard out or standard error, and if there's something we can change here. The logs from sqlcmd are not showing up in the github action logs, which are first parsed by Microsoft.Resources/deploymentScripts service. There should be a way to get the logs to show up and avoid the extra step of troubleshooting for the user.

[rajeshkamal5050]

@jongio can you take a look and see if we can

• add some retries?
• make sure it logs?

[jongio]

Retries being discussed here: Azure/bicep#1013

You can try to add a depends on for the database.