Deployment template can specify registryName, defaults to MCR

[brendankowitz]

Description

This pull request includes changes to the deployment configuration files to enhance consistency and flexibility. The most significant changes involve the introduction of a new registryName parameter.

Enhancements to deployment configuration:

• samples/templates/default-azuredeploy-docker.json: Added a new registryName parameter to specify the Docker registry containing images to deploy.
• samples/templates/default-azuredeploy-docker.json: Modified the linuxFxVersion and DOCKER_REGISTRY_SERVER_URL properties to use the new registryName parameter instead of a hardcoded value. [1] [2]

Removal of obsolete parameters:

• samples/templates/default-azuredeploy-docker.json: Removed the cosmosDbFreeTier parameter and its associated logic. [1] [2]

Other improvements:

• build/jobs/provision-deploy.yml: Added a new registryName variable to the provisioning script.
• samples/templates/default-azuredeploy-docker.json: Updated the default value for the imageTag parameter to "latest".

Related issues

Addresses #4806.

Testing

Describe how this change was tested.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)