This reverts commit 646489a3.

The debugger will use this to delay load Roslyn EnC until its needed.

* Build color schemes into pkgdef resources

* Add files to read items from PKGDEF files

* Apply ColorScheme PKGDEF as defaults colors

* Add ColorScheme dropdown to Advanced Options page

* Update formatting for contributed PkgDef files

* Add margin to custom theme warning

* Address ColorApplier feedback

* Updated based on PR feedback

* Change to a VsixColorCompiler package that includes VC runtime

* Remove VsixColorCompiler

* Move native methods

* Remove PKGDEF reading

* Add additional color options to ColorSchemeOptions

* Add color scheme reader for reading the scheme XML

* Add coverter for turning color schemed into registry entries

* Update applier to read schemes from xml

* Initialize applier on package load

* Update option pages to refresh onLoad

* Remove VsixColorCompiler PackageReference

* Implement feedback from Code Review

* More feedback from Code Review

* Update file headers

* WIP

* Resolve PR feedback

* Use SchemeName in place of name strings

* Fix options persistence

* Make OptionChanged event nullable

* Revert change to GlobalOptionService

* Revert to using VisualStudioWorkspace for accessingOptions

This reverts commit 6ac8006e.

* Document load failures

* Delete WorkspaceFailureOutputPane

* Remove dead code

* MSBuildWorkspace cleanup

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.

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

Now that the editor has their own public version of this API, and all
code has been migrated to use the new system, we can delete all of the
code that was supporting the old handlers. It may be surprising that
much of this code was dead, but the command handler list that was being
invoked by all of this was indeed empty.

The intent of this particular commit is to be a fairly mechanical change
that leaves other bugs or strangeness in place. In particular,
DebuggerIntelliSenseFilter had a special ExecuteVisualStudio2000 that
removes the buffer's read-only flag, but in many codepaths we never
set that back. In other cases, we also ignored the HRESULT that came
from the next filter in the chain. These all appear to be bugs, but I
won't touch them for now.

There's also some remaining work happening in
AbstractOleCommandTarget.Execute.cs that probably should either be moved
to the core editor code (if it wasn't already), or into the command
handlers of Roslyn itself.

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

* Remove old style command args and registration

we used to initialize those when packages are loaded. but with CPS, those packages are no longer automatically loaded with solution open (perf win)

so now, it is moved to VSWorkspace ctor and it gets initialized when the workspace is created.

considered making it on demand but due to reversed dependency (error reproting happening in lower layer), required some plumbing so looked into how expensive the initialization is. and it turns out due to previous work done in these area, initialization was quite cheap. any expensive one was already lazy or consumed by CPSProjectFactory already.

so, just moved initialization into VSWorkspace ctor and fixed MEF dependencies.

* 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

* renamed LogSummary to ReportTelemetry

* added telemetry to see how often partial solutoin is used

The previous implementation assumed that it'd get a call from the
old DocumentProvider to know when new files were opened so it could
add it to the list of frames. When I deleted the DocumentProvider, that
hookup wasn't working anymore, and so it would never be tracking
anything at all. Oops.

Rather than couple some types together, the implementation is now
more standalone. I've elected, rather than also listening to RDT events
to simply start tracking a frame the first time it's activated.
The only way I can think a document could be made visible without being
activated that we would care about is on first time load when we
re-open existing documents. If you had a bunch of documents open, and
they were in different frames/windows, we won't consider the non-active
documents to be visible until you first focus on them. I'm not sure this
is really much of a loss; we've often seen that many customers have
files reopened on them that they didn't care about, so this might
actually improve solution open performance since we won't be processing
files they may not care about.

This also brings the service up to a slightly more modern/correct
implementation. This is now a proper MEF part that doesn't assume it's
being created on the UI thread, and it manages it's own shutdown rather
than assuming the package will shut it down in the package unload.
The previous implementation also was a bit strange in that it was a
workspace service, but still had a singleton underlying the whole thing.
The singleton was broken in that different files might be in different
workspaces, but it would always give DocumentIds out for all of the
workspaces, despite it being documented as "only returns for the given
workspace". There's still a singleton doing all the Visual Studio
eventing, but there's now per-workspace logic to correctly filter it.

Unlike the previous implementation, this doesn't really do any cleanup
anymore other than ensure that the async tasks started are joined to
avoid things running after MEF shutdown. Practically, us unsubcribing
events brought no value to anything other than spending extra time
during shutdown, so we'll just leave that as is. It feels "wrong" but
it's the way many are arguing this should be done these days.

Lastly, this now uses async service provider to fetch services. Calls
for data do not block on the service provider having done that work,
since doing so would violate other parts of Roslyn assuming that we
wouldn't block on the UI. I think it's fine, since this service is
very much a tool for optimization only. It still uses JTF internally
on calls that we know are coming in from VS (namely, the .Dispose()) so
that's fine.

* added BulkFileOperation listener so that we can pause our ambient work while more important operation is running

* make it simpler