Add prompt to select virtual environment for the worskpace

[luabud]

If a global interpreter is selected and the extension detects the existence of a new virtual environment in the workspace (e.g. created in the terminal), we could add a prompt asking if the users would like to select it as the interpreter for the workspace.

[DonJayamanne]

We should do the same for:

• pipenv, as Pipenvs are also workspace specific.
• pyenv (existence of .python-version indicates the usage of pyenv)
  What do you think @luabud ?

[luabud]

For now we won't do it for pipenv and pyenv

[DonJayamanne]

Prescribed solution:

• When VSC loads if auto selected workspace interpreter != local virtual environment, then display prompt

  • When a new virtual environment is created (attach event handler to IInterpreterWatcher.onDidCreate, then proceed>
  • Check if user has specified interpreter in workspace settings.json.
  • Get a list of workspace virtual environments using ioc.get<IInterpreterLocatorService>(IInterpreterLocatorService, WORKSPACE_VIRTUAL_ENV_SERVICE).getInterpreters(...)
  • If there are items in the above list, then this means we have local workspace interpreters
  • Then display prompt to select the above virtual env (note: use IInterpreterHelper.getBestInterpreter to get the interpreter to use)
  • Add a do not show again button that will never show it for all workspaces

• Use const notificationPromptEnabled = this.persistentStateFactory.createWorkspace...PersistentState(deprecatedInfo....., true);

• Do not show again only applies to the current workpace.

[DonJayamanne]

@luabud

• Do we need a setting that will disable this prompt in every workspace folder
• E.g. assume I keep creating virtual envs in workspace folders, & I always select No for all folders. Do we then need a option so the user turn this prompt off completely.

[luabud]

Can we reopen this so we can remove the condition where this prompt appears only if there isn't an interpreter path set in the settings.json file?

[DonJayamanne]

@luabud please create a new issue instead, helps avoid confusions as well (specially with old comments).