* Support TimeTravelTraceInterop in function resolver.

- The function resolver isn't loaded when the base monitor is
TimeTravelTraceInterop, which needs it to resolve function for function
breakpoint.
- To add TimeTravelTraceInterop to the right vsdconfigxml file, I also
need to update some package so that it can be built.

* Address PR feedback.

- PrivateVisualStudioPackage isn't necessary since I set PrivateAssets=true in the package reference.

* Remove RoslynProjectType

* Remove ToolsVersion, namespace from Project tags

* Remove updating of MSBuildAllProjects

* Update BuildBoss

* Delete DeployTooolsetCompiler

This change is required in order to enable running on non-desktop TFM tests from VS test explorer window.

Based on work by @AArnott in dotnet/roslyn-sdk#240

This reverts commit b6285348.

* move StreamJsonRpc to 2.0

* use object and collection initializer

* changed to throw rather than return

* share JsonRpc creation when it can share code

* add linked files to share code

* more moving around so that we can have linked file working

* addressed PR feedback

* changed name to WatsonReporter

* moved to latest streamjson version

* added a way for partner to add thier own json converter to roslyn service hub service base type

* fixed test break.

it is caused by behavior changes between StreamJsonRpc 1.x and 2.x

* added comment follow PR feedbacks

* updated comment following feedbacks

The project which deploys ILASM tools ends up bringing two runtime
packages that have the same assets:

- runtime.win-x64.microsoft.netcore.runtime.coreclr
- runtime.win-x64.microsoft.netcore.app

Specifically assets like SOS.NetCore.dll exists at different versions in
these packages and end up getting copied twice to the output directory.
This double write ends up breaking our build (as well as basic
isolation).

The short term fix here is to no longer treat this as a code project but
instead a tools project. That eliminates the MS.NetCore.app package and
the associated double writes

Long term though the root issue needs to be addressed: making ilasm and
ildasm easier to deploy.

https://github.com/dotnet/coreclr/issues/15059

Microsoft.NETCore.App 3.0.0-preview4-27525-12, SDK version 3.0.100-preview4-010963

This cleans up all of the PROTOTYPE comments around using the 3.0 SDK
inside the DIM branch.

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19162.7

* Update CoreFX dependencies

* Generate suggested binding redirects

Fixes #31571
Fixes #33910

Now that we have the version of arcade that supports
Microsoft.Net.Compilers.Toolset we can remove a few work arounds.

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19066.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19067.6

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19068.4

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19069.2

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19070.2

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19072.5

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19073.5

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19080.6

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19081.3

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19101.16

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19102.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19103.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19104.18

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19105.5

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19106.4

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19107.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19108.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19112.3

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19113.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19114.4

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19115.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19119.2

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19121.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19121.5

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19122.3

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19123.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19124.1

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19125.2

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

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19126.6

This change enables C# 8.0 use in the code base as well as moving the
recommended Visual Studio version to 2019 Preview 4.  The following
features are now allowed to be used:

- `switch` expressions
- recursive pattern matching
- `using` declarations
- `static` local functions
- local / parameter shadowing in local functions / lambdas
- `null` coalescing assignment
- `async` streams: keep this out of our public API surface for now as we
don't want to block unification with netcoreapp in the future.

Before getting into the features which are off limits I wanted to
outline how compiler toolsets work in this repository. There are three
toolsets we need to consider when adopting new features:

1. The compiler toolset which provides the IDE experience: Intellisense,
syntax highlighting, etc ...
1. The compiler toolset which is used when the solution is built. This
is explicitly different than the compiler toolset which ships with the
MSBuild driving the compilation.
1. The compiler toolset is built from source on every PR and used as the
toolset for the PR (overriding 2 above).

That being said the following features are offlimit for now:

- Index / Range: the API surface area, including the parts the compiler
depends on, underwent significant churn for .NET Core Preview 3. Until
we converge it means toolsets 1 and 2 can be a bit out of sync.
- `unmanaged` generic `struct`: this is not included in VS2019 Preview 4
and hence using it would make the IDE experience poor.
- Nullable Reference Types: this area is under active churn and we could
easily get into a situation where toolsets 2 and 3 disagreed on code
checked into the repository creating unmergeable PRs. As such we're
holding off on this in master for now. Until then please use the branch
[features/NullableDogfood](https://github.com/dotnet/roslyn/tree/features/NullableDogfood)
to dogfood NRT. This will be merged back into master closer to
Dev16.0GA.

Note: This change only affects the C# compiler toolset. There are no
changes to our MSBuild or .NET Core SDK toolsets. Those will be coming
soonish though.

Closes #32540.
Closes #33083.

This version of the build task can run correctly on .NET Core 3.0. Our
current one is suffering from a private reflection bug that causes the
build tasks to crash on startup. This is the PR which previously fixed
that bug.

https://github.com/dotnet/roslyn/pull/31763

We had a non-trivial bit of code we would use to fetch ImageMonikers
from IVsHierarchies for use in the project drop down, but we would still
have to convert them into legacy imagelists because that's what the old
API expected. The editor added a new API that we could implement that
just works natively with ImageMonikers. Besides being generally ugly,
the old code also had lifetime problems where we might reuse image
lists between different calls and all sorts of badness would happen.

Unfortunately I can't delete all of the code that was doing the
conversion, because there is still one remaining use (the "preview
changes" dialog) that is still not moved over yet. I am deleting any
of the helper methods that were exclusively used in this path though.

Fixes dotnet/roslyn#28236.

This also lets us remove one special hack we had in place, since that's
included in current package versions.

* Updated dotnet build tools

* Add nuget.packaging dependency to RoslynPublish

Update the buildtools specifically for this fix dotnet/buildtools#2213