Bicep Deploy - Notify users of when parameters are not saved due to @secure

Currently in our deploy flow,

- User supplies us with No parameters file or a parameters file that does not provide a value for all of the parameters in the Bicep file
- User enters in values for each unanswered param
- We then ask, would you like to Create/Update your parameters file from values used in this deployment?
- At this point, if they say yes, we will not add any params to the created parameters.json with the @secure decorator

The functionality we want to add is, if the user answered @secure parameters during the deploy flow, we should pop up a notification in the bottom right each time that says "The params labeled with @secure were not saved. Params include: adminPW, kubernetPW"

A button of [OK] and [Do not show again] would be nice

No file, test, or entry point is named. Start by locating the deploy flow that collects unanswered parameters and creates the parameters.json file, then trace how @secure parameters are identified. Done means users are notified which secure parameters were not saved and can choose OK or Do not show again.

Written by the indexing model from the issue text.