Using revisions with bicep deployments

> Please provide us with the following information:
> ---------------------------------------------------------------

### This issue is for a: (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Mention any other details that might be useful
One really nice feature of container apps is using multiple revisions and Blue Green Deployments.

I tried to structure a deployment workflow around bicep templates like in this sample repo, but I was unable to get revisions to work correctly. Is this just something that will only be supported by using iterative deployments or will this be possible using the bicep deployment workflow as well?

Documentation or an example for this would be greatly appreciated!

Thanks in advance.

Review the sample repository's Bicep deployment workflow and the issue's references to multiple revisions, blue-green deployments, and iterative deployments. Determine whether revisions can be managed through the Bicep workflow, then add documentation or an example showing the supported deployment approach and its expected result.

Written by the indexing model from the issue text.