The plan for Aspire 9 is to support customization of the container app
for services by leveraging the CDK to generate the bicep IaC for a
given container app.

To prepare for that new world, we'd like `azd infra synth` to start
writing bicep and to modify our deployment strategy for container apps
to be based on ARM deployments instead of directly PUTing a copy of
the resource to the RP.

This change starts to work through that.

This adds rudimentary support for deploying the `.bicep` version of
the IaC for a container app as generated by `azd infra synth`.

In the case where both a `.yaml` and `.bicep` version of the IaC for a
container app exist, the container `.yaml` version is prefered.

When neither the `.yaml` or `.bicep` version of the IaC exist on disk,
`azd` will continue to generate and deploy the `.yaml` flavored
version of the container app IaC.

This change moves using bicep instead of yaml for container apps for
aspire projects behind the alpha flag
`aspire.useBicepForContainerApps`. To enable this, run `azd config set
alpha.aspire.useBicepForContainerApps on`.

Also adds support for using bicep when `infra synth` had not yet been run.

…bicep-for-container-deployment

…-use-bicep-for-container-deployment

…-use-bicep-for-container-deployment

…-use-bicep-for-container-deployment

…ttps://github.com/ellismg/azure-dev into ellismg/aspire-use-bicep-for-container-deployment

…-use-bicep-for-container-deployment