Additional functionality to Build-Bicep -GenerateParameterFile

[StefanIvemo]

Is your feature request related to a problem? Please describe.
The -GenerateParameterFile switch generates a parameter file with all parameters in the .bicep file. You should be able to specify what type of parameters should be added to the parameter file.

Describe the solution you'd like
-GenerateParameterFile should be a parameter supporting the following scenarios.

-GenerateParameterFile All - Should generate a parameter file with all parameters from template (Parameters with expressions should have expression as value)

-GenerateParameterFile Required - Should generate a parameter file with required parameters only

-GenerateParameterFile Default - Should generate a parameter file with all parameters that does not have an expression as default value

Additional context
Add any other context or screenshots about the feature request here.

[PalmEmanuel]

Should be connected to the functionality built in #28

[alex-frankel]

Can we also have functionality to only generate parameters, without transpiling the bicep code into the ARM template? Now that bicep works natively with PS and Az CLI, I want to build the parameters file from a bicep file and use that in my command as follows:

Generate-BicepParameters
az deployment sub create -f main.bicep -p main.parameters.json -l eastus -c

I want to recommend this module in response to this issue, but it appears this functionality is missing:
Azure/bicep#2626

[StefanIvemo]

@alex-frankel I will fix that, it's a great idea. Plan to ship a new release any day now and we already have the code for such a function from an earlier attempt to improve parameter files.

[alex-frankel]

Thanks! It would be awesome if you can jump into the above thread once it's released to let them know.

[StefanIvemo]

Created separate issue for the suggested new function to generate parameter files without transpiling the bicep file into ARM template #139