[LLDB] Shadowed variable printing behavior differs with PDB vs DWARF debug info

LLDB 23.1.0-rc3

Sample program (from Rust test suite):

```rust
fn main() {
let x = false;

zzz(); // #break
sentinel();

{
zzz(); // #break
sentinel();

let x = 10;

zzz(); // #break
sentinel();

{
zzz(); // #break
sentinel();

let x = 10.5f64;

zzz(); // #break
sentinel();
}

zzz(); // #break
sentinel();
}

zzz(); // #break
sentinel();
}

fn zzz() {()}
fn sentinel() {()}

```

When compiled for `windows-gnu` (i.e. DWARF debug info) printing `x` at each of the labelled breakpoints yields the following:

```
v x
(bool) x = false
c
...
v x
(bool) x = false
c
...
v x
(int) x = 10
c
...
v x
(int) x = 10
c
...
v x
(double) x = 10.5
c
...
v x
(int) x = 10
c
...
v x
(bool) x = false
```

When compiled for `windows-msvc`, each print yields `(bool) x = false`

LLDB-DAP is able to recognize the shadowed variable and the appropriate scopes for all 3 versions

but `v` always seems to choose to print the one in the oldest scope rather than the newest.

Start by reproducing the Rust sample under windows-gnu and windows-msvc, stopping at each labelled breakpoint and running `v x`. Compare LLDB's output with LLDB-DAP's recognized shadowed-variable scopes; done means `v x` selects the variable in the innermost active scope consistently across the nested scopes.

Written by the indexing model from the issue text.