The dependency projects serve a few purposes:

- Help ensure package unity by serving as a single place for a NuGet reference.
- Make NuGet updates simple by having a single place to change.
- Grouping together related packages to make it easy to take a dependency on say Visual Studio editor.

The first two points are largely obsolete now that our project.json references are strictly validated on every build and have a single update mechanism.  This meant a lot of our depnedency projects were just making Roslyn.sln bigger.

As such I went through and deleted all of them which had only 1 or 2 project.json entries.  I left the VS ones which tend to group 10+ references together.  They are still serving a valid "reference VS" purpose.

1. Reference a bunch of stuff from Nuget packages instead of VS.
2. Move to Update 2 versions of packages.
3. Now that we are using the packages, we're referencing
   Microsoft.VisualStudio.Shell.14.dll instead of .15 again.  This means
   that types that moved to Shell.Immutable.15 are not type forwarders.
   Luckily we didn't need anything from Shell.Immutable.15 in the project
   where it was a problem.

This reverts commit 760e1204.

This reverts commit e2fc5135.

Synchronize all corefx references to -23504 and bring in the
xunit coreclr test runner.

With Visual Studio 2015 Update 1 you should not specify -anycpu
in the runtimes section. Right now we'll have both to allow us to build
with and without Update 1, and we'll remove the old ones once we've
made the transition.

Update 1 also tries deploying implementations for some class libraries,
so I'm updating all our test and VSIX deployment class libraries to
now include implementations.