Add binding redirects for System.ValueTuple and System.Xml.ReaderWriter

[jcouv]

This is a mitigation for https://devdiv.visualstudio.com/DevDiv/_workitems/edit/467584

The issue is that when you install 4.7.1 after installing VS, the binaries that depend on "any facade that we have either introduced or that we have changed in 4.7.1" should be ngen'ed again, but they are not.
The impact is that the compiler (VBCSCompiler.exe, csc.exe, etc) is JIT'ed on every run, resulting is significant performance degradation (50%) which RPS caught.

This PR for 15.3 preview 2 adds binding redirects (without changing the version of the assemblies selected) as a mitigation. We verified those manually.

The binding redirects are shown below. They get added to 5 core binaries (csi, vbi, csc, vbc, VBCSCompiler) and also InteractiveHost.

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.ValueTuple" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.1.0" newVersion="4.0.1.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Xml.ReaderWriter" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
      </dependentAssembly>
    </assemblyBinding>

[jcouv]

@jaredpar @tmat @dotnet/roslyn-compiler for review.
FYI @AlexGhiondea @natidea

[tmat]

👍

[jcouv]

Test windows_debug_vs-integration_prtest please

[jcouv]

@agocke Can you also take a look?

[agocke]

LGTM

[jcouv]

Merging per thread with @natidea
Thanks

[jcouv]

Got some update from AlexG. It turns out the root cause is different than we thought. It was not an ngen problem per-se, but a problem with the config produced by VS which drives the ngen'ing process. That config differed from that of the compiler, so the compiler was not running the ngen'ed image.
The fix is still correct though.