When "viewing definition" of module, support a way to view the decompiled bicep instead of the ARM JSON.

**Is your feature request related to a problem? Please describe.**
For our engineers working with our customers, it's sometimes unclear what the source code is in an ACR-hosted template. This unfortunately leads us to a scenario in which we have to share the source code from our internal repos, while the template code is already present in the ACR. All our engineers have access to the ACR containing our bicep templates.

**Describe the solution you'd like**
We're very fond of snippets, and since we can reference templates and their properties in resource statements, we'd like to be able to expand templates stored in our ACR, from within our VSCode editor. For example:

Type `!acrname:path-in-acr-to-our-template` in your vscode, and via intellisense it auto-discovers which templates are stored with that name. When pressing enter, it will replace the statement (similar to `resource` or `res-app-plan`, for example) with the template file content. So if you'd have done that you'd see the whole stored template, instead of just a resource statement referring to the template in the ACR.

I understand it's not the way to use an ACR in a template, but knowing what the template content actually is would help our colleagues a lot. And prevents our colleagues from sharing repo access.

Start by reproducing the VS Code IntelliSense flow for module references to templates stored in ACR. Compare the current ARM JSON definition view with the requested decompiled Bicep or expanded template view, and determine how snippet replacement should behave. Done means an ACR-hosted module can be discovered and opened or expanded in the editor without requiring access to the source repository.

Written by the indexing model from the issue text.