Report the queried executable path in uv python list

[zanieb]

In an attempt to avoid reporting shims as their resolved sys.executable path, we report the queried executable path instead. This seems more correct for this command, broadly? Interestingly, it changes the reported paths for Homebrew Python

Closes #9979

[zanieb]

I can try to add some test coverage here, but it seems kind of tricky.

[zanieb]

@Gankra would you try this out on your bespoke Windows setup?

[Gankra]

Confirmed this is working the way you want:

cpython-3.13.2-windows-x86_64-none                   C:\ProgramData\chocolatey\bin\python3.13.exe
cpython-3.13.2-windows-x86_64-none                   C:\Users\gankra\AppData\Roaming\uv\python\cpython-3.13.2-windows-x86_64-none\python.exe
cpython-3.12.9-windows-x86_64-none                   <download available>
cpython-3.11.11-windows-x86_64-none                  C:\Users\gankra\AppData\Roaming\uv\python\cpython-3.11.11-windows-x86_64-none\python.exe

[Gankra]

Hmm wait does this change whether we actually invoke the shim? The "bug" was purely display?

[zanieb]

Can you say more? Interpreter discovery invokes each executable it finds. Previously, we reported sys.executable (which for a shim, is the resolved path) — now, we report the invoked executable (i.e., the path we discovered).

[Gankra]

The detail I was unclear on was whether we kept invoking through that executable once we found it, or if we cached the sys.executable path and used that directly.

[zanieb]

Well.. we keep invoking through sys.executable in general, because we never tracked the original path. In uv python list, we don't invoke the interpreter again.