Search for the VS install with the compiler package matching the target arch

[jtschuster]

DNNE searches for the newest VS with either x64 or arm64 compiler packages, no matter the target. Instead, search for the newest VS with the compiler package that matches the target of the compilation.

See dotnet/runtime#126673 and dotnet/runtime#126847

[MichalStrehovsky]

FWIW, in native AOT, we simply call vswhere.exe to find vcvarsall, and then we run it to set up paths in the documented environment variables and pull it out of that. Plus we have an opt out mechanism to skip all of that: https://github.com/dotnet/runtime/blob/main/src/coreclr/nativeaot/BuildIntegration/findvcvarsall.bat

[AaronRobinsonMSFT]

FWIW, in native AOT, we simply call vswhere.exe to find vcvarsall, and then we run it to set up paths in the documented environment variables and pull it out of that. Plus we have an opt out mechanism to skip all of that: https://github.com/dotnet/runtime/blob/main/src/coreclr/nativeaot/BuildIntegration/findvcvarsall.bat

I'm using the COM server that vswhere.exe uses. It is the same thing, but I don't need to process create.