Design for pipenvPath and poetryPath settings

[eleanorjboyd]

The following two settings exist right now:

Setting(python.)	Default	Description
pipenvPath	"pipenv"	Path to the pipenv executable to use for activation.
poetryPath	"poetry"	Specifies the location of the Poetry dependency manager executable, if installed. The default value "poetry" assumes the executable is in the current path.The Python extension uses this setting to install packages when Poetry is available and there's a poetry.lock file in the workspace folder.

These settings need to be clarified a bit now that the python envs ext exists. Here are the following questions:

1. If one of these setting is set, should all environments of that type be found or only the one set? Since for other managers we display all the venvs we can find do we want this to align or not?
2. do we need any validation on if the path exists when going through someone setting it?
3. How does this setting interact with the project settings where you set the default env manager for a given project? Does it just work with it where if an env is managed by poetry lets say, we always use the poetryPath but otherwise it wont be referenced?

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[eleanorjboyd]

@karthiknadig
@luabud