* Enable switching bitness of interactive host

* Improve integration test error reporting

* Update integration test

By default, VS sets the first project listed in the solution as the default project. This saves new contributors from having to manually set the default project.

This project originally existed to support a Dev14 vs. Dev15 split,
which we no longer version that way. This project had it's contents
moved out a few minor updates of Dev15 ago, and is now empty, only
so that way if you had an older VS Update F5 would still work. Now
we require 15.6 as a base drop, which also has this containing nothing,
so we can just delete this.

DevDivInsertionFiles.vbproj is the last project which isn't included in
Roslyn.sln. Included it there and remove the solution that used to drive
it's build.

* Remove src/Setup/DevDivPackagesRoslyn/

This contained a list of packages that we depended on and needed
facades deployed into Visual Studio. We already have
VisualStudioSetup.Dependencies that already (should have...) contained
all the facades and more. We can just consume that project instead
of having yet another duplication of facade lists.

* Fix casing

* Also include the CompilerExtension as a source of facades that we must include

This ensures that if the compiler adds a new facade but we don't update
VisualStudioSetup.Dependencies (either intentionally or by accident)
we still will include the right facades.

* Include DevDivPackagesDebugger into Roslyn.sln

By doing this, the VisualStudioSetup.Dependencies.csproj will now
figure out the highest version of our own dependencies and the debugger
dependencies, and create a single package that we can deploy that
contains all of them.

* Exclude inserting packages that are created by VS itself

* Remove ProjectGuid from DevDivPackagesDebugger.csproj

This makes BuildBoss happy.

This code was built as a prototype for porting the compiler server to
other platforms. It has now been ported to CoreCLR and multiple OSes
through multitargeting. The portable server cannot meet our security
requirements and will never ship, so it's continued existence in our
code is merely confusing to anyone who happens upon it.

* Source packages improvements

* Target net45

* Only generate source link when emitting PDBs

* Make BuildBoss happy

Merged it into the non-desktop specific project. Will make porting our
test projects to netcoreapp easier.

This is a standard tool in our repo. Looks like it was just omitted by
accident when it was originally authored.

It's gross, but we need to publish *something* until ILAsm is exposed as
a normal assembly

This is a (currently empty) project that will contain parts of
EditorFeatures that demand the WPF surface area.

We don't need the split anymore now that we're only supporting Dev15.

Unfortunately this required the introduction of a NuGet package that
has a namespace "Workspace" to our VS project, which meant I had to
disambiguate Workspace wherever it's used in that layer. I considered
doing an extern alias instead to disambiguate, but applying that to a
ProjectReference isn't supported. That's tracked by NuGet/Home#4989.

This primarily moves us to the 2.2.0 version of xunit. In order to make
that transition though a number of other changes needed to happen as
well:

1. Needed to move our desktop target to 4.6.1. This should've been
required some time ago but we were essentially depending on bugs in the
SDK / NuGet.
1. Remove the DeployCoreClrTestRuntime project. This entire idea
depended on having the xunit.console.netcore package. This has since
been deleted and doesn't work with the 2.0 SDK.
1. Remove the deploy compiler tools project. Can just use dotnet exec
now and that's much more efficient.
1. Resolve a new ambiguity with KeyValuePair. A helper of ours now
exists in netcoreapp2.0.

I fully expect a number of Jenkins legs to fail with this change: build
correctness, coreclr and ubuntu. But I want to validate our other legs
and am still trackind down answers needed to fix the others.

Portable unit tests now build their desktop variants directly to the
UnitTests directory in a runnable state. This allwos tests to be run
directly and removes the need for the desktop deployment project.

Our long term goal with asset publishing is to make it a completely
separate step from build. It's an operation which can optional be done
after builds complete. Even being done multiple times if needed to say
work around errors.

Additionally publish should be a deliberate, explicit operation. The
simple act of branching should not publish by default, it should be
explicitly opted into.

This moves us in that direction by doing the following:

- Centralizes our publish story to a single file: PublishData.json in
master
- Makes publish a step that can easily be run on any completed build
- Makes NuGet / VSIX publishing per branch and configurable. Allows for
uploads to many feeds if necessary
- Begins using dotnet/versions to track our packages.

Migrated the remainder of our code base to use the new SDK via the
ConvertPackageRef tool.

https://github.com/jaredpar/ConvertPackageRef

This changes are made by VS whenever Roslyn.sln is opened. Keeping them
as it appears to fix some configuration problems.

In theory this should only insert a build order dependency between these
projects.  Forcing TestUtilities.Desktop to build before the parent
project.

In the new SDK this is treated as an actual reference, not a build order
dependency.  This means that it eventually sees a NetStandard project
referencing a Desktop one and errors out.

Rename Microsoft.CodeAnalysis.Metadata project to Microsoft.CodeAnalysis.Debugging to match the namespace