This changes our .gitignore to consider .vscode as well as adding in an
initial tasks.json file for consideration. Still fairly new to Visual
Studio Code but been using this tasks.json file locally for a bit now
and have found it fairly productive

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

Remove diagnostics from error list on document close or reset for tha…

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

* Update list of C# Next features and reviewers

* Add pattern matching features

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

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

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

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

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

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

Add code action to extract local functions

Fix for configuring code style for "infer member names in anonymous types" persists the wrong setting 

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

Simplify how we compute and store the location we use to persist the sqlite storage cache.

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

Move LiveShare off of the deprecated constructors and project shims

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

Our package load does a bunch of specific things like setting up static
state and ensuring we have certain components loaded on the UI thread.
The InitOptionsAsync was doing just a small part of that, and missing
other things that had undefined behavior. This just loads the package
which is a bit heavy handed but at least ensures we won't have
differing behavior which is probably for the best until we delete all of
this.

Live Share was still using a bunch of deprecated shims which in some
cases were only existing to support this code. Delete it all and move
onto direct uses of the Workspaces API.

There appears to be a memory leak in the existing code: it doesn't
appear the projects that were created for Razor contained documents were
ever removed from the workspace. This maintains that leak since it's not
obvious how to fix it, but at least the leak is more obvious now.