We need xml files to report results to MicroBuild. This is what our
build queue expects but must have been broken semi-recently.

This PR fixes the CoreCLR compiler server on Windows and changes our bootstrap 
build to act as a test case. The build was previously failing during pipe ownership verification
because the required API was not available through reflection. This change
uses the System.IO.Pipes.AccessControl API to do pipe ownership verification
instead. However, System.IO.Pipes.AccessControl is operating system dependent 
and thus ends up in the runtimes subdirectory next to the build task.
Unfortunately, there is no mechanism for automatic assembly resolution
of plugin DLLs like MSBuild tasks, so we have to implement something
similar ourselves. This change hooks assembly resolution and, when we
see a well-known DLL request, we redirect it to the appropriate path.

Fixes #20900 and #24072

Can now specify "-binaryLog" to Build.cmd and it will produce a binary
log for every invocation of MSBuild. The logs will be written out to the
`Binaries\Logs` directory.

The dotnet pack command can't handle nuspec files (or at least I can't
find the appropriate documentation for it). As such contining to use it
for creating NuGet packages for now.

These were moved in https://github.com/dotnet/roslyn-sdk/pull/21

Need to wrap the property group in the test Directory.Build.props file
with a PropertyGroup.

VS should be inheritting the %TEMP% value we are setting. On the off
chance it gets the original value though lets copy the props / targets
files there to see if this is the cause of the hang.

The repository is fully converted over to the new SDK but there were
still a few remaining references to the classic SDK in the central build
targets. Removing them now that they are no longer needed.

These projects are no longer needed. Removing them.

Historically these were used to create an uber VSIX that nested all of
our other VSIX for a single deployment point. In practice though we have
not actually used these. The install / uninstall issues around them are
too problematic.

Should the uninstall issues be fixed we will consider bringing these
back

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

All of the XML literals in the file use the same xmlns value. Set a
global import so we can simplify the building of the literals.

Can now specify "-binaryLog" to Build.cmd and it will produce a binary
log for every invocation of MSBuild. The logs will be written out to the
`Binaries\Logs` directory.

The VS insertion items require a bit more work to be a part of batch
signing. In particular the VSMAN files because they contain checksums of
many of our other assets. These need to be rewritten during batch
signing to have the new correct values.

These assets though aren't actually required to be signed though. Hence
for now just moving the building of them till after signing completes.

These assets already have a correct strong name as they are signed with
a full key. They only need a certificate signing.

Remove the assembly version plumbing as it's no longer needed by our
build.

The Insertion directory is no longer created during our normal build.
Rather it's created as a separate, publishing step that occurs after
build.

After this move the `-buildAll` switch will now build the entirety of
the Roslyn source tree. Previously it didn't build a number of items
related to VS insertion. That layering was arbitrary and mostly due to
limitations in our signing process. Now it can all be done in a single
phase.

The SignTool now supports batch signing NuPkg in the same manner as
VSIX. Simplifying our infrastructure now to build everything and then
sign as a final step.

This commit just moves the sign phase after packing. The next set of
commits will merge more of the Microbuild logic into build.ps1.

This will produce more detailed logs that will help the SDK
team track down a few CI issues.

Now that we are targeting 4.6.1 there is a new redirect we need to add
to our unit tests.