When the pinned SDK changes, C# Dev Kit should inform the user that a reload of the window is required

[phil-allen-msft]

Describe the Issue

When the pinned SDK changes by editing global.json, C# DevKit should help the user get into the new state that the user has taken clear steps to switch to.

Steps To Reproduce

1. Boot VS Code with C# DevKit installed.
2. Open a folder with a global.json that references an SDK incompatible with the projects in the folder (net10 TFM with global.json 9.0.3xx)
3. Notice a number of warnings and restore errors.
4. Change global.json to enable the desired TFM.
5. Work for a while

RESULT:
Lots of bits of C# Dev Kit don't work as expected, most notably (but definitely not limited to) the TestExplorer.

MOST LIKELY:
Similar issues when switching branches if the global.json changes as part of the branch switch (or pull of changes from remote)

Expected Behavior

Optimally, C# DevKit would just restart any processes impacted by the current SDK with the new SDK and carry on; that's likely not a cheap option. A simpler option would be to inform the user that they have a simple operation to carry out to get into a working state.

Environment Information

No response

[claudiaregio]

@phenning when we review the workspace requirements experience let's make sure to find a way to re-trigger the window if something changes, I don't think we've baked in that logic yet.

[vsccarl]

Status: Fixed