Consolidate C# and VB language servers into one implementation

* EnC: Use the current document encoding when reading source text from file.

* Optimization

* Update dependencies from https://github.com/dotnet/arcade build 20191204.4

- Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19604.4

* Update dependencies from https://github.com/dotnet/arcade build 20191205.6

- Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19605.6

Avoid going into an infinite cycle while resolving erroneous event/property implementation within an interface (#40175)

Fixes https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1029574.

* Document load failures

* Delete WorkspaceFailureOutputPane

* Remove dead code

* MSBuildWorkspace cleanup

Co-Authored-By: NSam Harwell <sam@tunnelvisionlabs.com>

Move to new API for GetSuggestedActions

Merge branch 'master-vs-deps' to master

Fixes #39888

Skip failing C# REPL integration tests.

After CI image was updated with 16.4 Preview 5 some REPL tests started
failing consistently. https://github.com/dotnet/roslyn/issues/40160

Nullable collections

Merge master to master-vs-deps

Merge master to master-vs-deps

* Make finding checksum async
* Clean up TryRunCodeAnalysisRemoteAsync

Fixes #39975

- Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19603.17

Merge master to master-vs-deps

Enable nullability checking in more of our collection types

Remove the nullable wrappers from the Workspaces layer

* Refactoring

* Refactoring

* Refactoring

* Feedback

* Misc feedback

* Use ValueTask instead of custom task caching

Merge master to master-vs-deps

Visual Studio Code Tasks

We weren't ensuring the the tuple elements had top-level nullability
if we inferred the pattern was itself using nullable.

This clarifies why we are stripping the nullability, and replaces it
with the "not null" instead of "oblivious" which generates to the same
code but is a bit more correct if something else tried to operate on
the type symbol.

In the deepest of ironies, the extension methods we had to wrap
top-level nullability was implicitly hiding a potential null reference.
Removing the extension methods is now flagging this, so this fixes it
up. The handling isn't ideal: if we don't have a Task<T> we won't
necessarily wrap, but that's not something really worth going out of
our way to support -- most code doesn't.

The compiler merged support for top-level symbol nullability in
https://github.com/dotnet/roslyn/pull/39498, so we can now delete our
own wrappers that were performing the same thing. This is a mostly
mechanical change.

For places where we were calling LookupSymbols or ClassifyConversion,
those places previously called .WithoutNullability() since the compiler
API would have thrown if we gave it our wrappers, but the APIs had
otherwise no way to pass top-leve nullability. That was an accepted
oversight at the time, and the belief is passing in the full symbol
will generally be more correct.