MCP Server Tool for generating Bicep parameters files to be used for Snapshots as test files

**Is your feature request related to a problem? Please describe.**
I have recently blogged about snapshots https://cloudadministrator.net/2026/02/18/azure-bicep-snapshots-test-and-validate-your-code-and-deployments/ and now with latest release they are GA. It will be helpful if there is MCP tool that analyze the schema (user-defined data types) of a module and generate multiple bicep parameter files that represents different test scenarios. This is also related to #18918 as that one will be needed to analyze the schema of a module and #19089. Modules can have complex parameters array of objects within array of objects, objects with discriminator types, etc. The point is to be able to test all paths of the code and see if the generated output is the one that is expected. When you are updating a module by having new release that is either breaking change release, feature release or bug fixes via those tests you can catch issues with the code you are adding like:

* Verifying that you are not introducing any new bug.
* Verifying that the added feature is applied according to the expected results.
* Verifying code that it works before actual Azure deployment thus reducing development time. Running bicep snapshots is faster than actual deployment on Azure. You will still have to run deployment on Azure to verify completely your code but you can fix code bugs faster.

The data that will be filled can be just mockup data as when you doing this locally as long as the values for the parameters/properties match the schema of the module that is good enough data to generate snapshot and verify your code. For example if somewhere a parameter requires subscription ID value like 00000000-0000-0000-0000-000000000000 can be added, if somewhere it is needed name for Log Analytics workspace it can be just filled with value workspace01, etc.

**Describe the solution you'd like**
Just tell Copilot in VSC to generate test (bicep parameters) files for all possible scenarios of the module and after a few minutes you get bicep parameters files with different names representing different scenarios available in specific folder of your repository.

The issue names no source files, tests, or entry points. Start by locating the MCP server tooling and Bicep snapshot-test infrastructure, then determine how module schemas and test scenarios are represented; done means generating multiple valid parameter files that cover the module's possible paths.

Written by the indexing model from the issue text.