Lightbulb for Edit rule in configuration file

[ucheNkadiCode]

Via #5314, we will be removing the lightbulb that automatically turns off a rule in the bicep config file.

From @StephenWeatherford's idea, we should look to add a lightbulb that allows the user to edit the rule in the configuration file by opening it and (hopefully) taking them to that rule in question. This does a few things

• Reduces confusion of "which lightbulb does what" and disallows the user from mistakenly clicking a lightbulb that turns off the rule for good when that is a behavior we would like to avoid
• Gives the user an easy way to turn off, OR, increase the level from warning to error
• Allows the user to gain observability of the available rules they can change

Note: This option would be shown BELOW the disable next line issue

[ucheNkadiCode]

In a lightbulb the user will see "Edit in configuration file" -> if they do not have one we will create a config file, then hopefully we can create the rule in the file if it does not already exist and highlight the word "warning"

This allows the user to now turn it off or set it to "error" level

[ucheNkadiCode]

Updates to this flow:

Change "Configure" to -> "Edit rule in config file" -> if the user cares about the specific name of the rule, we'll ultimately take them to see it in the config file, plus I may be wrong but I think hovering over it/disable next line also shows them the rule? I think some of the rule names are very long so it's cleaner to just say "edit rule".

If there is no Bicep config file found, we should popup an intermediate step of a notification:

"No Bicep config file found, would you like to add a Bicep config file to the workspace root?" [Add File] [Cancel]

Added related information to #5866

[StephenWeatherford]

• telemetry
• What if multiple violations of same rule in range?
• More manual testing