Extend bicep visualizer to display Azure Verified Module (or any module) components

[SteveMacNZ]

When using Azure Verified Modules (AVM) in bicep deployment templates, bicep visualizer will only show the AVM modules as a folder without any details on the resources that are being called within the AVM module, like snippit below, The AVM modules can contain mulitple different resource components depending on the parameters passed. for example the virtual-network AVM module can create the vNet, subnets, diagonstic settings, peerings,resource locks etc.

Currently to work around this, to create documentation need to copy the AVM main.bicep for the module into code and run visualizer on that which displays all possible resource components, including ones that you are not deploying.

Ideally I would like to see the bicep visualizer being able to display the called resources in the AVM modules - possibly displaying the module name with the folder reference like its currently displaying but using avm:module rather than just and then displaying the called resources branching off that folder.

previously incorrectly raised under VS Code issue microsoft/vscode#240569