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

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.

At this point, the nullable support in the semantic model seems stable,
and there's no reason for somebody to manually turn this on since any
project that is using nullable will turn it on automatically.

Revert the functionality to show info bar to make editorconfig a solution item for existing solutions with existing editorconfig

1. IDE code fix that adds new editorconfig for configuring code style/severity has been updated to create the file at root of the solution, instead of the project. Additionally, the code fix also automatically adds the file as a solution item.
2. We now detect if user opens a solution with editorconfig at the root of the solution and provide an info bar to make it a solution item with a single click. User can choose to silence this suggestion for the current solution (solution user option) OR silence it for all solutions for the user (workspace option).

* Both columns added

* Genericize custom column names

* More changes to genericize

* Cleanup

* Respond to feedback

* WIP

* Change tuple to properties

* Restrict to just containing types

* Cleanup

* cleanup

* Refactor

* Change method for getting Containing Type and Member

* refactor GetAdditionalProperties

* Fix merge conflicts

* respond to feedback

* respond to feedback

* Change to struct

* Add type for AbstractCustomColumnDefinitionWithMultipleValues

* Cleanup

* Change AdditionalProperty to FindUsagesProperty

* respond to feedback

* respond to feedback

* Hide columns in F#

* respond to feedback

* fix merge conflict

* Change from hiding columns to removing columns for non supported langs

* Add additional implementations

* formatting

changed our task center status bar to say "low priority background process" rather than "live analysis" to reduce confusion on what "live analysis" means since term "live analysis" has strong association with "errors" in VS.

also, it now shows ## of pending work and whether BG process is paused or not.

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).

At this point, the flighting controls we have aren't really useful
anymore: we want this on for everybody unless the opt out, and that
opt-out would be specific to certain users that are running into issues
with the new system to keep them unblocked. I'm keeping this a per-
machine setting (that doesn't roam) because it's really repo or VS
version specific.

Addresses part of https://github.com/dotnet/roslyn-analyzers/issues/2023

This PR converts our current experimental feature that recommends installation of [FxCopAnalyzers VSIX](https://marketplace.visualstudio.com/items?itemName=VisualStudioPlatformTeam.MicrosoftCodeAnalysis2019) into a non-experimental feature that recommends installation of [FxCopAnalyzers NuGet or VSIX](https://docs.microsoft.com/en-us/visualstudio/code-quality/install-fxcop-analyzers?view=vs-2019).
All the experimental checks have been removed, but I have retained all the existing logic about when the infor bar shows up (light bulb invoked on 3 separate days for separate VS sessions).

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/824308/

In Naming Styles, we previously hadn't been localizing the "Symbol Kinds" list, along with the other two lists there (Accessibilities and Modifiers). We've decided to loc just the "Symbol Kinds" list because the other two lists are exclusively language keywords.

* Wip

* Update more pages

* Formatting

* Respond to feedback

* Add spacing to Formatting General page

* changed the way we report live analysis to task center

previously, we listen to diagnostic service to report progress. problem is that, it only raise event if it found errors on a file. so what we report is actually last file we found errors on rather than file that we are analyzing.

this caused confusion since we report in task center that we are analyzing file "A" when it is actually "analyzed" not "analyzing"

another issue is since it only report file that contains errors. we might not actually show anything in task center if there is no error, or show file "A" for long time if that is only file with errors.

this PR changes the experience closer to what users would expects. and now progress is for solution crawler not specifically on diagnostics.

now we report file that solution crawler is analyzing.

there is still cavet such as solution cralwer can pause between processing a file if VS is busy. but it will still show file "A". or we will not update UI at least 200ms a part and etc.

since it is task center where we don't want to be too impactful to VS, based on feeedback we will see whether we need to do more such as detect solution crawlwer pause and update task center to show pasue. or update task center to show different stage such as analyzing/analyzed.

or show in task center, what analyzer is actually running such as diagnostic, todo, designer attribute scan, find all reference cache and etc.

* addressing PR feedbacks

* [WIP] first draft to move to new code lens API

* rename SemanticChangeTracker to WorkspaceChangeTracker since reference counter can change without semantic changes (such as method body change causing reference to be added or removed)

* created new dll for new code lens OOP. can't use existing VS dlls since it has more dependencies than what CodeLens can provide. we don't control code lens OOP so new dll with only depdencies required for code lens.

* fix resource id name

* pass in cancellation token on place it is missing

* ServiceHubServiceBase no longer expose Rpc directly

* address PR feedbacks

* fixed build break due to the merge

* fixed nuget version conflicts

* fixed designtime dll issue

* moved to new APIs that fix staled spans

* updated to versions suggested by editor team

* PR feedbacks

* Addressed PR feedbacks