Add "Run Code Analysis" command support for Solution explorer "Analyzer and Code Cleanup" project context menu

Fixes #38051: Users can now use this command to force complete all the analyzers on a project/solution (includes NuGet based + VSIX based analyzers, including IDE code style analyzers).
Complements #39544: Users can now potentially disable continuous analyzer execution  during live analysis and instead execute them on demand with these commands.

Few things to note:
1. This change hooks up new "Run Code Analysis on ProjectName" menu commands for CPS based managed projects. These commands are already hooked up for csproj based legacy projects in StanCore, but that should eventually go away.
2. This change only hooks up these new commands for top level Build and Analyze menus. Adding these to "Analyzer and Code Cleanup" context menus for project/solution in solution explorer is much trickier as the command groups are defined in StanCore. I will do so in a separate PR.
3. This change also exposes a "RunAnalyzers" API for StanCore, so we can trigger analyzer execution when user executes run code analysis on solution/csproj based project. There is a VS side PR that will consume this functionality to make the experience uniform across all "Run Code Analysis" commands.

Hook up the configure severity context menu commands and functionality from a context menu in error list that shows up when a diagnostic entry is right clicked. For now, we allow configuration only if a single configurable diagnostic is selected. In future, we may allow bulk selection and configuration (IMO that doesn't seem like a very useful scenario, unlike bulk suppression from error list where individual diagnostic instances are suppressed).

1. Renamed "Set Rule Set Severity" command to "Set severity". Also renamed "Info" and "Hidden" sub-menus to "Suggestion" and "Silent" respectively to align with our editorconfig severity terminology.
2. The set severity command handler checks if the project uses no ruleset or the default built-in ruleset, and if so it adds or updates editorconfig to configure severity. Otherwise, we continue using specified ruleset for configuration.
3. Updated the effective ruleset severity computation for the rule nodes under Analyzers node to account for severity settings from editorconfig (analyzer config documents).

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

* Remove old style command args and registration

This is a reworked version of #32616 targeting the dev16.0-preview3 branch.