Same venv show twice

[joshspicer]

Testing #458

Steps

1. Create new folder and open as workspace. Workspace is empty
2. Use the new project button to create python module with a venv
3. 🐛 There are two venvs shown. The first one shouldn't be there, there is no /Users/jospicer/ttest/.venv

[eleanorjboyd]

expanded on the steps:

1. created a new folder (ttest) has no env
2. go through "new project" flow, with setting to create an env
3. project "hehe_project" is created with .venv located in it
4. projects view updates to show both ttest and hehe both pointed at the hehe_project/.venv

under discussion:

• does it make sense to set the ttest env as the nested hehe_project/.venv? Or will this confuse people?
• should the root ttest be listed in the project view?

cc @cwebster-99 and @karthiknadig

[cwebster-99]

Adding some notes from offline discussion:
The root folder (`ttest I believe) would (should've) be listed automatically in the projects view but prior to creating the virtual environment it was set to a global python. Once a virtual environment is created in the workspace , we favor the venv over a global python. Whether or not we should favor a virtual venv from a nested folder is up for question vs keeping the global selected. I need to think more about this flow though to have a confident answer.

Another thought to consider is that only hehe has python files in it.....does it make sense to not show a folder in the project view until it has python files? So in this case ttest wouldn't be listed until the creation of the nested folder with Python files. This doesnt prevent both ttest and hehe showing up after venv creation since technically ttest has python code in the nested structure but maybe that offers another lens for us to think about this flow? This might be problematic from the "start from scratch" flows where users build up their project piece by piece

[eleanorjboyd]

related to: #491

[eleanorjboyd]

1. To confirm, the parent folder ttest should already be in the projects list when opened
2. If the virtual environment exists in a nested folder (not at the root), should it still be favored over a global interpreter?
3. Should folders (like ttest) be shown in the Projects view only after they contain Python files? (follow up would hiding folders until they contain Python files negatively impact workflows where users gradually build their project structure?)

summarized questions we are looking to answer