Problem

Fixes #1882.

While stopped at a breakpoint, a watch / evaluate request for a naked variable could return the value from a parent scope instead of the current one. Given:

$myVarName = 123
& {
    $myVarName = 456
    $myVarName   # break here
}

evaluating $myVarName returned 123 instead of 456, even though the Variables explorer (and PowerShell itself) correctly show 456.

Cause

DebugService.GetVariableFromExpression searched the flat variables list with FirstOrDefault. That list is populated broadest-to-narrowest (global → script → local → stack frames), so the global/parent copy of a shadowed name was always matched first.

Fix

Search the Local, Script, then Global scope containers in that order first, falling back to the full flat list so frame-only names still resolve. This matches PowerShell's own variable resolution and what the Variables explorer displays. Only the name lookup changed; ID-based lookups elsewhere are unaffected.

Testing

• Added DebuggerResolvesVariableFromMostLocalScope plus a shared VariableScopeTest.ps1 that shadows a variable across scopes and asserts the local value wins.
• Confirmed it fails without the fix (returns the parent value) and passes with it.
• All 36 DebugServiceTests pass on net8.0.