This fixes the ability to build with later versions of Visual Studio
on your machine, since some later versions are incorrectly embedding
type forwards to assemblies that they shouldn't be. The NuGet package
includes dependencies of

- Microsoft.VisualStudio.OLE.Interop
- Microsoft.VisualStudio.Shell.Interop
- Microsoft.VisualStudio.TextManager.Interop
- Microsoft.VisualStudio.Shell.Immutable.11.0

automatically, and so I remove those from the project files now too.

DevEnvDir is safe to use everywhere.

We conditionally add this in a target to work around Visual Studio's
poor handling of conditions on Reference nodes in the project system.

In future versions of Shell.14.0, some types have been type forwarded
to this assembly. This means we'll take a reference to Immutable.14.0
when building with 14.0, but that's fine since we won't use it.

If we don't have this, CreatePkgDef is getting angry. My guess is the
assembly is no longer in the GAC, and so it's being implicitly relied on
that the assembly is copied by MSBuild for CreatePkgDef to find it.

This is just so it's not the only project in our entire source tree
doing something different.

For the Shell binary, we have two choices. We could either reference the
version that matches the version of Visual Studio you are building with,
or we could reference a fixed version with a HintPath so we can find the
binary on all versions of Visual Studio. Doing the former is tricky
since the name of the assembly is embedded into some XAML, so I go with
the latter option.

This is the implementation assembly with implementation details that
we should not depend upon from our shipping binaries.

This has been set for all releases we care about, so we can delete this.

This doesn't hardcode an assumption on 14.0.

PIAs always have the version of the Visual Studio they shipped with,
even in higher versions of Visual Studio. We should reference the fixed
version that matches the PIA.

We use some public types from assemblies that aren't in the SDK. We
previously picked those up from the GAC but there's no guarantee that
they are there.

Set up roslyn to use dynamic windows images

Revert "Disable archiving temporarily to avoid issues with the size of the ar…"

Fix for #9463: Async rewriter to fail gracefully when types are missing

Disable archiving temporarily to avoid issues with the size of the ar…

Perf Metrics with CPC instead of WallTimeMS

Move nuspecs to open

Build the correct name for paths

Update project.lock.jsons

The code for building names for dependencies was using ChangeExtension instead of just appending
the .dll extension.  This allowed for entries like MS.CA and MS.CA.CSharp to have the same
hash in specific cases.

In the absence of the CPC tool and other related tools that help in
producing metrics, the user should be able to run the tests and get some
basic metrics.