Clean up the remaining solutions to have the utilities included.

Add Razor Language Service shim for accessing the remote client

Add Razor Remote Workspace shim for getting access to the solution in
the ServiceHub process. This relies on the same set of Roslyn services
being called by the client to initialize state in the remote process.

Add overloads to the 'remote' solution service to avoid a need for IVT in
in the Razor Remote Workspace shim. Checksum is internal to Workspace.

The dependency projects were added as a way to help unify our project.json references.  Instead of every project referencing the NuGet package, we had a dependency project which referenced it and everyone referenced that dependency project.  Due to the transitive nature of NuGet it would be roughly equivalent.

This system had a number of downsides:

1. There was no enforcement.  Even though dependency projects existed, there was no mechanism to force developers to use them.
2. Getting the granularity correct was tricky.
3. The projects themselves have special props / targets to get them to produce no output.  This can trip up MSBuild up to date checks.

Since then though we've begun using RepoUtil to verify our NuGet reference correctness.  This removed the need for these projects and hence I'm removing them from our build.

Fixes #7895

The NuSpec file for the compiler is missing a number of facades.  This flaw's been around for some time in a few forms but it's gone un-noticed due to our reflection magic around facades.  Now that the magic is gone we're finding places where the NuSpec is incorrect.

This change both fixes the NuSpec and adds verification that it is correct.  The strategy for correctness is to build a deployment project which contains all of the deliverables in the NuSpec.  Namely:

- csc.exe
- vbc.exe
- csi.exe
- Microsoft.Build.Tasks.CodeAnalysis.dll

The MSBuild process will deploy all facades necessary for execution to the output directory.  That makes it possible to do a simple check that the output and NuSpec are consistent with each other.

TLDR: artifacts are going to move around in Binaries\Debug and the directory is going to get a lot bigger.

At a high level build projects can be classified into three categories based on how they write output:

- incorrect: a given output path is written to more than once with different contents
- less correct: a given output path is written to more than once but always with the same content
- correct: a given output path is written to exactly once

Today the roslyn build is decidedly “incorrect” as pretty much every file is written directly into Binaries\Debug. This means it ends up writing pretty much every Visual Studio SDK DLL twice: once for Dev14 and once for Dev15. For example at various points in the build Binaries\Debug\Microsoft.VisualStudio.Text.Data.dll may refer to Dev14 and at others it’s Dev15. If this seems like a scary proposition for a build that’s because it is indeed scary and it has real consequences. By now pretty much everyone on the team has hit the build race condition that is dragging down our PRs.

The general fix here is to move build outputs into separate directories. Instead of building to $(Configuration) projects now build into say $(Configuration)\Exes\$(MSBuildProjectFileName). This will have a substantial increase in the size of Binaries. We will be looking into ways to reduce that. In the short term though build stability far outweighs the size increase.

This change takes us most of the way to "correct". There are several places I had to compromise in order to get this initial change in:

- UnitTests still build to a common output folder (one for Dev14, another for Dev15). Pulling unit tests apart is going to take a bit of work.
- Every project has a <RoslynProjectType> entry. This will go away in the future for most projects. It's temporarily needed so I can fix roslyn-internal in parallel without taking down the build.
- VSL.Imports.targets is messy. Unavoidable for now due to the above. It will get cleaner as I iterate on this.

None of these are relevant to the underlying race condition. Hence it's okay to push them off.

this is to make develop - debug cycle easiler when adding new features to service hub.

to enable this, turn on Roslyn/FeatureManager/Features/RemoteHost and RemoteHostInProc

once enabled, InProcRemoteHostClient will be used instead of ServiceHubRemoteHostClient

except concrete type of RemoteHostClient, all other parts, exactly same code will be used.

InProcRemoteHostClient can be used in unit test to test client and server side as they are.

The tool now lives under dotnet/roslyn-tools.