"Resolving SDK" messages aren't attributed to an evaluation

[rainersigwald]

Issue Description

@KirillOsenkov was looking at an internal build failure that was hard to diagnose, in part because the Resolving SDK events aren't parented under any particular project evaluation

Steps to Reproduce

#7988 should show these symptoms too.

Expected Behavior

If SDK resolution fails, all of the messages should be attributed to a project, so it's easier to understand what was looking for the SDK and any progress messages/warnings associated with it.

Actual Behavior

Analysis

This may be caused by the desire to single-instance SDK resolution for a build, so the actual resolution is happening in one thread while other things wait on it.

Versions & Configurations

No response

[KirillOsenkov]

Potentially related location:
https://github.com/dotnet/sdk/blob/3dc5e528fffc050cace4cff8bc32954eb33f0455/src/Resolvers/Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver/CachingWorkloadResolver.cs#L121-L136