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

### 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

https://github.com/dotnet/msbuild/issues/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_

Reproduce the behavior using dotnet/msbuild#7988 and inspect the SDK resolution and project-evaluation event handling. Trace how SDK resolution messages are emitted and determine how they can remain associated with the project evaluation that requested them. Done means resolution failures, progress messages, and warnings are attributed to the relevant project evaluation.

Written by the indexing model from the issue text.