Enable verbose output in VSCode/VS extensions and --verbose flag in Bicep CLI

**Is your feature request related to a problem? Please describe.**
There is a lack of visibility regarding the actions that are being taken both by the Bicep extension for vs code as well as the operations executed by the bicep CLI. As a direct consequence troubleshooting is much harder since it requires more in-depth understanding of the code execution and development expertise to reverse engineer the flow of control being done by the extension/cli

**Describe the solution you'd like**
We should enable a `verbose` setting and flag for extension and cli so that debug logs are available for users when they need to troubleshoot. Debug logs would contain amongst other things the current directory of execution and the steps being executed by the system processing of the Bicep manifests

## Additional Info

Related to discussion in https://github.com/Azure/bicep/issues/9902

Start by reading the related discussion in issue 9902, then trace the VS Code extension and Bicep CLI entry points involved in processing manifests. Define the verbose setting and CLI flag scope, including which execution details and debug logs are required; the work is done when both surfaces provide consistent, useful troubleshooting output.

Written by the indexing model from the issue text.