Add check for minimum `xcopy-msbuild` version in the CI

[dkurepa]

The following scenario has happened to us a few times already:

• We get a dependency update from arcade, bumping the sdk version
• The PR is merged, everything looks good
• We start the staging pipeline, and the required validation is yellow, and all jobs are failing with the same error, saying that the new SDK requires a higher version of msbuild

Often, we don't catch these errors fast, we may even finish some releases with them.

We should add a check in the CI pipeline that would use any arcade task, requiring us to use the latest sdk that's in arcade, notifying us early if we have to update xcopy-msbuild in global.json

Release Note Category

• [ ] Feature changes/additions
• [ ] Bug fixes
• [x] Internal Infrastructure Improvements

Release Note Description

Get early notification if xcopy-msbuild needs to be bumped

[pavel-purma]

@dkurepa do you know why do we even need xcopy-msbuild in dotnet release repo?

[dkurepa]

There used to be an error that happened often while dotnet-release was on arcade main, where the pipeline would complain that the msbuild installed on the pipeline agent was a lower version than the new sdk needed. This xcopy-msbuild was a way to install and use newer msbuild, so the pipeline could run. It might not be needed anymore, since we're on .NET 8 and not latest