Part of https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1065328

* AssetProvider refactoring

* Remove usage of SessionWithSolution

* Move Razor specific service base

* Add TypeScript external access APIs

* Make IVSTypeScriptDiagnosticAnalyzerImplementation optional.

* Add wrappers for ContainedDocument and ContainedLanguage

We recently changed this code to switch from using the Workspace Options setter (now deprecated) to Workspace.TryApplyChanges. This causes an intermittent exception [here](https://github.com/dotnet/roslyn/blob/aeb47891e92341b700c3a290a92553b8a91b445a/src/VisualStudio/Core/Def/Implementation/ProjectSystem/VisualStudioWorkspaceImpl.cs#L374-L377) when TryApplyChanges is invoked from a background thread.

Fixes internal Watson bug [#1062942](https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1062942)

* Use Microsoft.NET.Sdk.WindowsDesktop for XAML projects

This API has always accepted null as a shortcut for an empty array, so
this annotates it accordingly.

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

* Move "is telemetry allowed" flag to DiagnosticAnalyzerInfoCache

* Clean up DiagnosticService

* Fixes

* Remove analyzer exception telemetry reporting.

* Remove reporting analyzer exceptions from SupportedDiagnostics.

The diagnostics will be reported when the compiler runs the analyzer on the compilation.

* Remove unused parameter

* Clean up analyzer telemetry reporting.

* Test fixes

* Feedback

When renaming a document, we ensure that the name is unique
but include the old document name in the check. Since that's
the document that's name is changing, we can ignore it
when comparing names for uniqueness.

Previously we reported diagnostics caused by the debuggee not allowing edits in the corresponding module in EnC diagnostic analyzer.
A module does not support edits if any of its instances does not support the edits. There are scenarios in which module instances may be loaded while in break mode.
E.g. if the user attaches to a secondary process while debugging a primary process, the secondary process might have a module instance loaded of the same module loaded to the primary process.
To handle these cases we hooked up debugger module load/unload events and invalidated the reported diagnostics.

This approach has a few problems:
1) EnC analyzer is now non-deterministic, as it can give different answers for the same inputs depending on the state of the debuggee
2) Turns out that the debugger does not deliver module load/unload events in all cases (e.g. when the secondary process is killed).
3) It's a bit complicated and would get even more complicated once we moved EnC to OOP/Cloud

Instead, we don't report these errors until the user triggers the "continue" action. At this point the VS and all processes being debugged are blocked until the changes analyzed and applied.
Since this situation is not very common the slight regression in interactivity is acceptable.

fix for language code capitalization

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

EnC: Tweak handling of out-of-sync documents to work around source file content inconsistencies (#40947)

* Do not block in presence of out-of-sync documents.

Instead, ignore any changes made to these documents while debugging until their content matches the source used to build the baseline DLL.

* Only check output PDB, not debugger SymReader, for document checksums.
Turns out SymReader does not support reading document checksums once EnC changes have been applied.

Better handle errors that might occur when validating checksums. Previously some of the errors were not reported as diagnostics.

We previously blocked EnC when we observed a source file that is out-of-sync (i.e. its current content does not match the checksum in the originally built PDB). We can however just ignore these files and report a warning that changes made to this file won’t be applied until the file content is reverted back to the state it was when the PDB was built (the file transitions to “matching” state). Once a file is in matching state it can’t change back to another state. We know that we have not applied any change to the code that was compiled from the file because we ignored the file while it was in out-of-sync state. Therefore we know that any changes made from now on can be safely applied to the debuggee.

If we can’t determine whether a file matches or not due to error reading the PDB or the source file content we can treat it similarly to out-of-sync file. That is, ignore any changes until we are able to confirm the file matches. That can happen if, e.g. the PDB is temporarily locked by another process and unlocked later.

Simplify implementation of GetStatusAsync.

Fixes VSO [1051496](https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1051496) ([VS feedback](https://developercommunity.visualstudio.com/content/problem/880533/edits-were-made-which-cannot-be-compiled-stop-debu.html))

Follow-up to https://github.com/dotnet/roslyn/pull/40289

Workspace options should now be set with `Workspace.TryApplyChanges(Workspace.CurrentSolution.WithOptions(newOptions))`