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.

this will cache compilation end analyzer info in diagnostic service so that
it can be cheap except the very first time that most likely done by solution crawler.

added tests

* remove usings when format document

* sort usings when format document

* add code fix

* hack fix for the issue with apply multiple changes.

* refactoring

* 3 changes

1. put open file editorconfig change tracking back
2. handle open file leaking when solution close with files opened case
3. don't share locks between editorconfig events and roslyn events

* skip the 'Remove unused variable' when format document

* changed code fix part to use "fix all" and only fixes P1 list rather than fix everything in the document. also not apply changes to buffer until everything is done rather than doing it per fix.

* made undo experience better

* add expression body as one of fix to offer

* add code fix options in format document settings

* add hidden box IsCodeCleanupConfiguredCheckBox to track if the user ever configured the code cleanup

* clean up

* fix some tests

* disable a test temporarily

* PR comments

* refactoring

* Revert "3 changes"

This reverts commit 7e0fd53f02a0e20d063440b3cce5569e51e71afc.

* PR comments

* PR comments

* renaming

* bug fixing

* PR comments

* refactoring

* refactoring

* refactoring

* refactoring

* Make ICodeCleanupService extend ILanguageService

* refactoring

* refactoring

* fix deadlock, call Format inside CodeCleanupService

* rename async methods

* PR comments

* move files under features

* PR comments

* PR comments

* Never Show this again will never show the code cleanup info bar for this user.

* rename

* use ImmutableArray

This reverts commit 720f5c5e, reversing
changes made to 6a6043c3.

changes include
make SourceText::GetChecksum and AnalyzerTelemetry contructor public.

added MustRunInProc in IBuiltInAnalyzer and some clean up around serializing Solution/Project/DocumentId and how DocumentState is exposed.

simplified temporary storage service's temporary storage management and added ability to attach to existing temporary storage

solution checksum and serialization service.

added remote host client
- this gives an ability for host (vs) to talk to remote host (service hub)

rename and moving files between feature/workspace layers
- only real change is having ICompilerDiagnosticAnalyzer interface which can either have inproc implementation or out of proc implementation.
- inproc is needed since diagnostics are in feature layer and one who uses feature layer out side of VS host need an implementation.

added RemoteWorkspace
- RemoteWorkspace has host agnostic implementation of roslyn features/services/workspace that will run in remote host

added service hub component and setup project for service hub
- service hub component is basically thin layer that deals with converting data to pass in to RemoteWorkspace

made devdiv insertion tool to ignore servicehub related files

support byte and char array natively in ObjectReader/Writer

this gives an ability for host (vs) to talk to remote host (service hub)

since this logic is now exposed to outside of engine, engine needs to be guarded from abuser so, logic is added to drop cache if there is too many high priority work. before only engine can decide what is high priority or not.

now, error list will have column (which is off by default) that shows source of each errors in a
format "assembly name" for analyzers node. and "assembly name" [vsix name] for vsix

Fix CodeFixService.GetProjectDiagnostics to handle compilation end diagnostics. Currently it was just force computing all document diagnostics, not the project diagnostics, which executes the compilation end actions.
Additionally, also fix the BatchFixAllProvider to correctly handle compilation end diagnostics.

previously we made system to prefer live diagnostic over build diagnostic.
also when we merge those two, we used very detail info to find out build and live diagnostics are same or not.

but the issue was diagnostics from build didn't have all information live one has, also diagnostics from build is static
when live one is changing as user type in IDE. which lead to race where build diagnostic might be already out-dated on arrival.

new system is that we prefer diagnostic from build over live. and don't distinguish them by detail info but whether live can produce
same diagnostics build produced. as user change file, we will replace build diagnostics in affected files to live diagnostics.

this should remove chance where build diagnostic got stuck in the system until next build. and as user change files, live diagnostic
over take build diagnostics.

Add the `GetDiagnosticDescriptors(DiagnosticAnalyzer)` method to the
`IDiagnosticAnalyzerService` interface.

put middle man in between diagnostic incremental analyzer so that two version can be changed without re-starting VS.

     Background:

     As discussed in the dev team all hands all code under the GitHub dotnet foundation is using a single process for contribution, API review, infrastructure and coding style. The idea is to present a unified view to our customer and give them a single story for contributing to any project under the dotnet foundation.

     https://github.com/dotnet/corefx/wiki/Contributing#c-coding-style

     The coding style transition is automated using a Roslyn based rewrite tool:

     https://github.com/dotnet/codeformatter

     This will be applied in stages across our developer tree. Right now the focus is on the Open directory as this is what is being presented on github. Code owners will be contacted before the transition happens.

     Note: this is a soft style requirement. There are no build errors that come from this change.
 (changeset 1408227)