We support configuration for boolean and enum based code style option values. The only unsupported current code style option from this fixer is specification of modifiers order, which is a custom user supplied string.

Fixes #33082

Alternate approach to track mapping from IDE diagnostic IDs to corresponding code style options that can be used to configure the diagnostic's severity. We now require each code style analyzer to provide the option at the constructor where it also passes in the diagnostic ID.

Revert "Add a language service to map all the IDE diagnostic IDs to an unique editorconfig code style option, if any such option exists. This service is used by Configure Severity code action to enable configuring IDE code style diagnostics using syntax: `%option_name% = %option_value%:%severity%`"

This reverts commit 1fb9371c.

Add a language service to map all the IDE diagnostic IDs to an unique editorconfig code style option, if any such option exists. This service is used by Configure Severity code action to enable configuring IDE code style diagnostics using syntax: `%option_name% = %option_value%:%severity%`
Remaining IDE diagnostics and all third party diagnostics would be configured using syntax: `dotnet_diagnostc.DiagnosticId.severity = %severity%` by this code action.

I have also added unit tests that ensure that all new IDE diagnostics are explicitly handled in this service to choose the appropriate syntax based on added options.

The code is updated to always assume this is true.

* Add Sort Usings command back to the Edit > IntelliSense menu

* Remove old style command args and registration