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 brought along some references to Microsoft.VisualStudio.Threading
that we previously didn't have. Nothing was wrong with this, but it
meant I had to fix some namespace qualifications that were assuming the
"Threading" namespace was unambiguous.

To prevent projects across the tree from having different dependencies, we unify
external package dependencies by creating empty C# projects that represent them.
We then make use of project.json package inheritance (where a project inherits
all packages dependencies from their dependencies) to unify it across the tree.

No projects outside of this tree, should be directly referencing versions of
these dependencies manually.

For this check-in I've tackled Metadata, Reflection, and DiaSymReader. Will tackle
the rest in future commits.

Rebase fixup

This reverts commit cfa447a6.

Also add support for completion item filtering.