https://github.com/dotnet/roslyn/issues/11512

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems?id=233669.

Add a version header to Object-Streams.  This way we can tell, up front if the persistence version has changed, and if we can read the data properly or not.

This reverts commit 7dd78ae8, reversing
changes made to 449f5586.

We have seen two big analyzer packages (CodeCracker and RefactoringEssentials) end up with registering async actions, which can crash VS from the async continuations.
See [this](https://github.com/code-cracker/code-cracker/issues/375#issue-87474837) for more details. Now we prevent this by disallowing analyzers to register async callbacks.

Fixes https://github.com/dotnet/roslyn/issues/13120

* Implement source link feature

* Fix CommonCompiler to open source link stream, add E2E tests

* Reduce code duplication across VB and C#

Revert "Revert "Revert "Revert "*DON'T MERGE INTO MASTER* Hide IOperation API behind a feature flag""""

This reverts commit d4d502e4.

This reverts commit a96d7825.

This reverts commit 92ff3f8d.

This reverts commit b03e8478.

https://github.com/dotnet/roslyn/commit/b03e84783806dc48f240e56188e6473323dc3ba1

The flag name is "IOperation". Register opeartion actions and calling
SemanticModel.GetOperation while the feature is disabled will throw an
InvalidOperationException. Also log a non-fatal-watson when
SemanticModel.GetOperation crashes.

Code cracker recently added an analyzer that accidentally reports diagnostics with a location in a syntax tree outside of the current compilation. We were not handling this case gracefully and causing VS to crash. Code cracker fixed their analyzer and released an updated package. This change guards against such cases by ignoring such diagnostics and reporting an analyzer exception diagnostic about invalid diagnostic.

Fixes #7173

Handle in-memory assemblies correctly in ScriptOptions.AddReference and when adding reference to the host object