[main] Update dependencies from dotnet/linker

[dotnet-maestro]

This pull request updates the following dependencies

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

• Subscription: 0d6d6ae4-f71f-4395-53e6-08d8e409d87d
• Build: 20220502.2
• Date Produced: May 2, 2022 7:52:17 PM UTC
• Commit: 05a3b652d525acaac1307221b62db979d0108692
• Branch: refs/heads/main

• Updates:
  • Microsoft.NET.ILLink.Tasks: from 7.0.100-1.22226.3 to 7.0.100-1.22252.2

[marek-safar]

@vitek-karas could you look into a new error?

[vitek-karas]

This is analyzer failure on ILGenerator.cs:1140 (and others) the code pattern looks like this:

private const string ConsoleTypeFullName = "System.Console, System.Console";

private void Method()
{
    Type.GetType(ConsoleTypeFullName, throwOnError: true); // IL2057
}

In linker this doesn't happen because the const field is effectively "inlined" into the IL by the compiler, so linker sees a constant string value and can resolve it. But analyzer apparently doesn't.

I'll look a bit more into this if the analyzer could figure this out, if not easily we will just suppress it for now and probably change the analyzer to not produce a warning in this case (ignore the problem).

[vitek-karas]

dotnet/linker#2774 - this will teach the analyzer to recognize const fields and improve data flow tracking in such cases.

[vitek-karas]

The fix on the analyzer side has been merged. Waiting for DARC to pick it up once a new build is available.

[tannergooding]

This should unblock #68612

[tannergooding]

Is Maestro auto-merge tracking the skipped checks as failures?

[vitek-karas]

I will merge this and take the maestro issue offline with the right people.