Revert bad changes from merge forward PR

[jkotalik]

Fixes #21630 (comment)

cc @dougbu

[dougbu]

Narrow this two just eng/Version*.* and you're done.

[jkotalik]

@dougbu if you are in a hurry, feel free to merge this before validation to get #21630 moving.

[dougbu]

I'm really starting to hate desktop msbuild ☹️

[dougbu]

If the Helix build succeeds, I'm going to ignore that OOM. But, I'm going to let the current build finish. (FYI Helix jobs don't get canceled when the pipeline that submitted them is canceled. So, canceling a build doesn't clean up as much as you'd like.)

[dougbu]

A fix we made to src/Framework/ref/Microsoft.AspNetCore.App.Ref.csproj in d99e7fe broke this build. Suggest we just leave things alone since #21630 is validating 🆗 and we can undo the src/Framework/ref/Microsoft.AspNetCore.App.Ref.csproj change only after that goes in. #21630 also overwrites some of the versions in this PR and the next dependency update will make everything coherent again.

That is, if I'm correct, let's get #21630 in and close this PR.

[jkotalik]

I'm a little uncertain about the action plan then. So what you are saying is:

1. Close this PR.
2. Merge [master] Update dependencies from dotnet/arcade dotnet/aspnetcore-tooling #21630
3. Reopen another PR to revert the Microsoft.AspNetCore.App.Ref.csproj

Is that correct?

[dougbu]

@jkotalik yes you've got the plan down. #21630 is in (hurray 🚀) and the last bullet can happen whenever

Reopen another PR to revert the Microsoft.AspNetCore.App.Ref.csproj

/fyi that change worked around an inconsistency between the incoming packages from dotnet/runtime that goes away now that we're targeting net5.0 too.