Prompt about environments upon user action rather than at start-up

[kimadeline]

For #19099

Find all the spots in the extension where Python is actually needed to run code, to figure out how late we can display a "Please install Python" prompt, instead of swarming the screen with "Python is not installed" notifications

[karrtikr]

Related: #19175

[karrtikr]

Investigate extension entry points which trigger prompts if no Python is available

Manually triggers:

• Execution of files in terminal Do not trigger any commands which requires an interpreter if an invalid interpreter is selected #19481
• Execution of files in REPL Do not trigger any commands which requires an interpreter if an invalid interpreter is selected #19481
• Debugging Do not trigger any commands which requires an interpreter if an invalid interpreter is selected #19481
• Refactoring
  • Pylance: Refactoring doesn't require interpreter
  • Jedi: Provides no refactoring
  • isort extension Do not trigger any commands which requires an interpreter if an invalid interpreter is selected #19481
  • isort Do not trigger any commands which requires an interpreter if an invalid interpreter is selected #19481
• Testing Do not trigger test discovery if an invalid interpreter is selected for the workspace #19465
• Interpreter changed Trigger environment prompt if an invalid interpreter is selected #19472
• Linting
  • Legacy
  • Restart server command Expose a way to trigger environment prompts for other extensions #19450
• Formatting
  • Legacy
  • Restart server command Expose a way to trigger environment prompts for other extensions #19450

Auto triggers at startup:

• Diagnostics regarding Python: Ensure Python is not installed and Invalid Python Interpreter
  • Provide an API to trigger the "No Interpreter" diagnostic upon user action #19396
  • Ensure it does not show up at startup Ensure prompts related to environment selection do not show up at startup #19483
• Intellisense
  • Jedi Do not attempt to launch Jedi server in case when Python is not installed #19395
  • Pylance: starts without any prompt, auto-complete for various stubs available
• Testing if auto configured to run Do not trigger test discovery if an invalid interpreter is selected for the workspace #19465
• Linting
  • If auto configured to run
  • Do not attempt to launch any servers in case when Python is not installed vscode-pylint#135
• Formatting
  • If auto configured to run
  • Do not attempt to launch any servers in case when Python is not installed vscode-black-formatter#94
• Any extension created via tools template Do not attempt to launch any servers in case when Python is not installed vscode-python-tools-extension-template#25

Possible enhancements:

• Have the "Install Python" command from the walkthrough open and fill in the suggested command #19448
• Explore ways to indicate to user whether Python is not installed or is invalid #19480

[karthiknadig]

@karrtikr You also need execution in background scenario.

[karrtikr]

Execution in background does not really affect the Getting started experience, unless it leads to errors that show up as a prompt. Hence it's not included.

[karthiknadig]

@karrtikr Jedi can be broken by the execution in background right?

[karthiknadig]

Never mind, you have that covered.