Ensure msbuild from vs usage is validated in arcade or arcade-validation

• This issue is blocking
• This issue is causing unreasonable pain

We had a bug that went through the entire validation and promotion process without being caught because it only surfaces when using the desktop msbuild from vs (not the xcopyable one)

See: #7558 and #7563 for context.

We should make sure we have some sort of validation (ideally as early as possible, during the arcade PR build) for this failure mode across branches.

I would like this done as part of FR. These validation holes end up being really noisy when they manage to get to consumer repos. Not only do they end up blocking a dev's entire day while they follow the fix around and make sure it gets to repos, but it erodes the confidence in arcade updates. @ilyas1974 feel free to take it out if you think this is out of scope.

[ilyas1974]

I think we can handle this in FR. As this does not have direct customer impact at this time, it will be something we address as time allows.

[michellemcdaniel]

Unfortunately, just passing in -msbuildEngine vs on an arcade build as an extra leg did not work. It complains that there is no vs object on the tools object in the global.json. So I grabbed a thing from aspnetcore (who does have the vs object) and tried adding that to arcade's global.json, which caused all of the windows builds to break, saying that it can't find the sdk.

It was not possible to find any installed .NET SDKs.

Going to try a few more things. Also curious how arcade validation doesn't already catch this, given that we do official builds on the important repos before promoting.

Also curious how arcade validation doesn't already catch this, given that we do official builds on the important repos before promoting.

We do not build any other repos anymore as part of promotion.

[michellemcdaniel]

Oh.

[michellemcdaniel]

Throwing this back to triage