[release/7.0] Update dependencies from dotnet/arcade

[dotnet-maestro]

This pull request updates the following dependencies

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

• Subscription: a1e8257b-e869-4455-b087-08da7ef6355d
• Build: 20220908.5
• Date Produced: September 9, 2022 5:25:04 AM UTC
• Commit: 622c2dc5ced5df5af002a3b06a52f9584b726b28
• Branch: refs/heads/release/7.0

• Updates:
  • Microsoft.DotNet.Arcade.Sdk: from 7.0.0-beta.22423.1 to 7.0.0-beta.22458.5
  • Microsoft.DotNet.Build.Tasks.Installers: from 7.0.0-beta.22423.1 to 7.0.0-beta.22458.5
  • Microsoft.DotNet.Build.Tasks.Templating: from 7.0.0-beta.22423.1 to 7.0.0-beta.22458.5
  • Microsoft.DotNet.Helix.Sdk: from 7.0.0-beta.22423.1 to 7.0.0-beta.22458.5

• Updates to .NET SDKs:
  • Updates sdk.version to 7.0.100-rc.1.22425.9
  • Updates tools.dotnet to 7.0.100-rc.1.22425.9

[ghost]

Auto-approving dependency update.

[MackinnonBuck]

@JamesNK I see you've done some work on DataProtection trimming - would you be able to take a look at these warnings?

[JamesNK]

Fixed new data protection trim warning.

[joperezr]

Would be good for somebody to validate, but the remaining errors are all link warnings of type:
Unused 'UnconditionalSuppressMessageAttribute' for warning 'IL2077'. Consider removing the unused warning suppression. which I believe is a new warning on the linker. I've pulled this locally and just added the NoWarn="IL2121" to the ILLink task invocation on projects WasmLinkerTest.csproj and LinkabilityChecker.csproj and the build passes. it would be good to get either someone from the linker team or the aspnet team to validate the right way to move forward, since this PR is currently blocking the update of dotnet/runtime in PR #43904

[joperezr]

After a closer look, seems like the warnings are mainly caused by - now unnecessary - warning suppressions passed to the linker. They were probably needed before but the linker must now understand that they are not needed.

[JamesNK]

Great, IL2121 is back.

We dealt with it in the main branch in this PR - #43028 (comment)

The changes may need to be made to release/7.0. You can look at the changes and see the places IL2121 was added to suppressions.

[TanayParikh]

The changes may need to be made to release/7.0. You can look at the changes and see the places IL2121 was added to suppressions.

43467be

[TanayParikh]

@JamesNK @joperezr looks like we're still encountering IL2121 despite 43467be, any idea what may be going on here?

[joperezr]

As an FYI, this is no longer blocking the ingestion from dotnet/runtime as the one change that required the SDK bump was rolled back temporarily. If we want to merge this PR, we can just revert the global.json change that is bumping the SDK which will get rid of all of the new IL warnings. That said, the change in dotnet/runtime will be redone after RC1 ships, and there will be a new SDK bump to match RC1 version, and at that point we will need to fix all of the warnings that the new SDK causes.

[dougbu]

@TanayParikh let's hold off until RC1 ships and we can use the released RC1 SDK. I'd rather not undo the IL-related changes only to need them reinvented later this week.

[JamesNK]

I think the solution here is a lot of the changes - trimming and no warn - from #43028 should be applied.

And I noticed I fixed the same trimming issue in a different way in this PR than in main. I want to update this PR to be the same.