Windows store Pythons can be detected (and skipped) twice

[davidhewitt]

Bug Description

Found while reviewing #2750

If an incompatible store Python is installed, it'll be found from the py launcher and potentially also from the pythonX.Y alias.

I think the fix is probably as simple as recording the paths of rejected interpreters and check that set before calling windows_interpreter_no_build.

🔗 Found pyo3 bindings
👽 3.10 is installed for win-amd64, while the target is not. Skipping.
👽 3.10 is installed for win-amd64, while the target is not. Skipping.
🐍 Found CPython 3.13 at C:\Users\david\AppData\Local\Python\pythoncore-3.13-arm64\python.exe

Your maturin version (maturin --version)

main

Your Python version (python -V)

N/A

Your pip version (pip -V)

N/A

What bindings you're using

None

Does cargo build work?

• Yes, it works

If on windows, have you checked that you aren't accidentally using unix path (those with the forward slash /)?

• Yes

Steps to Reproduce

1. Install py launcher
2. Install any windows store Python not compatible with current target, e.g. x64 Python when building for Arm64