Proposal: Consolidate all Bicep clients to use one single Bicep installation

Whenever there's a new Bicep version, I'm required to update three distinct Bicep installations on my machine:

- Bicep CLI (for PowerShell Bicep support)
- Azure Bicep CLI
- VSCode Bicep extension

This is very cumbersome, time consuming, error prone, frustrating and a waste of resources.

Please consolidate all clients of Bicep CLI to use only one single, same Bicep implementation. So, updating one of them will update them all.

If appropriate, feel free add a new option to each client to be able to determine a different, distinct Bicep installation path.

No files or tests are identified. Start by locating the integration points for PowerShell Bicep support, the Azure Bicep CLI, and the VSCode Bicep extension; done means these clients use one shared Bicep installation, with distinct installation paths supported if appropriate.

Written by the indexing model from the issue text.