fix global python interpreter filtering in Project Wizard

[sharon-wang]

Addresses

• Workbench: Positron new Project cannot use Python versions not on the path? #5341
• "No environment providers were found" for new Python project using New Project Wizard #4270

Implementation

• add new command python.isGlobalPython to the Python extension
  • Given a python interpreter path, return whether it is a global python interpreter
• remove RuntimeFilter, PythonRuntimeFilter and runtimeSource filtering logic from the Project Wizard, which would require an update to the appropriate enum every time we want to recognize a specific runtimeSource as a permitted "Global Python"
• rework _getFilteredInterpreters() to return all interpreters, only global interpreters, or undefined depending on the current state of the project wizard
• add/update log messages in the Project Wizard state handling methods

QA Notes

On Windows, MicrosoftStore-installed Python versions should now show in the Project Wizard interpreter dropdown when creating a new Venv.

On other operating systems, Global, Pyenv, Unknown and any other "Global" Python installations should show in the Project Wizard interpreter dropdown when creating a new Venv.

[seeM]

Code changes look good! I haven't been able to test the behavior on macOS because of another issue below, you could have someone else test on this branch or have it QA'd after merge.

---

I'm seeing a weird issue where the interpreter dropdown doesn't work when I've selected venv. It happens on the latest release for me as well so it is probably unrelated. Here's a video. Any idea what's happening here? Maybe it's a weird Python env on my laptop?

Screen.Recording.2024-11-26.at.11.55.45.mov

[sharon-wang]

I was able to reproduce and I think this could be related to #3061. Posted a comment over there with some recordings!

If you move the Project Wizard closer to the top of the screen and click the dropdown, does it show then? If you have a lot of interpreters paired with not enough vertical space, I think that's when this issue occurs.

[seeM]

@sharon-wang ah yes that moving the modal does fix the dropdown for me, great catch!