Bicep deploy - more options or visibility into extension-created parameters file path

**Is your feature request related to a problem? Please describe.**
When using the Bicep Deploy feature in the VS Code extension with no parameters file specified, I asked the extension to create a file based on the parameters I supplied and was expecting a prompt for a "save as" path. Instead, the extension automatically picks a path and saves to it.

If the default path (`.parameters.json`) is already taken, I see a prompt asking if I want to overwrite the file, but my only options are yes/no. If I select "no," then the parameters are not saved to disk, and I am not able to save the parameters to a different path.

**Describe the solution you'd like**
Ideally, users could pick a path to save the parameters file when the extension creates one. When creating a new file (either with the default path or a user-supplied path), the extension should log a message indicating that a parameter file was created and include a clickable path.