No engine work

And feed it back into the grid

Literally just the button, nothing happens when you click it. However, the button is accessible and INPC unit tested.

1. Make the strings sentence cased
2. Rename "Open Documents And Projects" to "Open documents" as per internal review.

And feed it back into the grid

Literally just the button, nothing happens when you click it. However, the button is accessible and INPC unit tested.

Revert "Switch the error list scope combo box to match the newly selected background analysis scope in Tools Options."

This reverts commit be5bd275.

Switch the error list scope combo box to match the newly selected background analysis scope in Tools Options.

Address PM feedback and change the user facing resource strings to match the error list terms in its scope filter combo box

`Active file` -> `Current Document`
`Open files and projects -> `Open Documents and Projects`
`Full Solution` -> `Entire Solution`

Replaces the existing "Full Solution Analysis" option, with a background analysis scope to allow users to control the analysis scope for all solution crawler based background analysis.

Fixes #38429. Active file scope minimizes all the background analysis to the active files, saving on CPU consumption from background analysis on remaining files in the solution.

I have also updated up the low virtual memory listener which detects low VM and used to turn off just the full solution analysis to now set the background analysis scope to "Active file" for the current session.

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.