[release/7.0.2xx] Update dependencies from dotnet/msbuild

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/dotnet/msbuild

• Subscription: 3911f289-5d48-4a76-3776-08daa2f83374
• Build: 20221207.2
• Date Produced: December 7, 2022 3:30:11 AM UTC
• Commit: c5532da3a3c99817e70d95fe9e07302ba72ee523
• Branch: refs/heads/main

• Updates:
  • Microsoft.Build: from 17.5.0-preview-22606-02 to 17.5.0-preview-22607-02
  • Microsoft.Build.Localization: from 17.5.0-preview-22606-02 to 17.5.0-preview-22607-02

[marcpopMSFT]

@jaredpar it happened again in this PR where razor csproj had a copy problem:
D:\a\1\s\src\RazorSdk\Tasks\Microsoft.NET.Sdk.Razor.Tasks.csproj(107,5): error MSB3026: Could not copy "D:\a\1\s\src\RazorSdk\Targets\Sdk.Razor.CurrentVersion.targets" to "D:\a\1\s\artifacts\bin\Release\Sdks\Microsoft.NET.Sdk.Razor\targets\Sdk.Razor.CurrentVersion.targets". Beginning retry 1 in 1000ms. The process cannot access the file 'D:\a\1\s\artifacts\bin\Release\Sdks\Microsoft.NET.Sdk.Razor\targets\Sdk.Razor.CurrentVersion.targets' because it is being used by another process. [TargetFramework=net7.0]

[jaredpar]

@marcpopMSFT but how can we reproduce the build locally? As mentioned in the issue I've tried re-running the entire command locally but can't see any items in the ItemGroup that causes the error. That makes it very difficult to fix because I can't see if I'm having any impact on the problem.

To me this seems to be the fundamental problem. If we can't reporduce the build locally, or at least similulate most of the behavior, then how are we supposed to make this any better? Any fixes seem like they're guessing at the behavior. Retries are just masking the actual problems. On the other hand, if we can reproduce the build behavior locally then we can start making real improvements here.

[marcpopMSFT]

Timing issues are going to be difficult to reproduce by their nature. I'd also ask if there was a way to essentially run the yml locally as that's your best way of recreating the exact environment. The next closest thing is running that msbuild command I sent you but any environment variables set would be different.