This change also separates implementation of ISymbol interfaces from internal symbols in C# compiler.

* Remove project type from Bing URI

* Add Language to DiagnosticData

* Trim arguments that are too long

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.

Respect RunAnalyzers and RunCodeAnalysisDuringLiveAnalysis project properties for VSIX analyzer execution

We recently added project properties for configuring analyzer execution during build and live analysis, see documentation [here](https://docs.microsoft.com/visualstudio/code-quality/disable-code-analysis). Currently, these properties are only respected for NuGet based analyzers. This PR adds support to respect these properties even for VSIX based analyzers, including the built-in IDE code style analyzers. https://github.com/dotnet/project-system/pull/5598 passes the required properties down to the Roslyn langauge service, and this PR consumes these properties and adds this support.

* Add solution crawler wrapper types

* Add Experimentation wrapper

* Add UnitTestingPinnedSolutionInfoWrapper

* Add KeepAliveSessionWrapper

* Add PersistentStorageLocationService wrapper

* Add UnitTestingWorkspaceTaskSchedule wrapper

* Add extension wrapper

* Change Workspace wrapper to an extension class

* Add more wrapper types

* Rename and remove files

* Add immutable array extensions

* remove lut ivt

* Remove the dependency on ServicehubBase

* Remove all the dependency for LUT

* Rename and remove unused wrappers

* Add comments

* Rename wrappers and accessors

* More renaming

Enable logging of informational telemetry for analyzers/fixers/refactorings executed during Ctrl + .

If user enables informational RoslynEventSource telemetry following the steps at https://aka.ms/reportPerf, we log the execution times for each analyzer/fixer/refactorings when computing the code fixes and refactorings to show in the light bulb. This will help us identify slow analyzers/fixers/refactorings that lead to UI delays with "Gathering suggestions" dialog.

Co-Authored-By: NJason Malinowski <jason@jason-m.com>

* EnC: Compare document content before performing IO while stepping

* Feedback

Co-Authored-By: NJoey Robichaud <joseph.robichaud@microsoft.com>

* EnC: Recover from unexpected exceptions in Emit, ReadChecksum

* Fix typo