Support multiple python versions for in-project virtual environment management

The current scenario when virtualenvs.in-project = true is specified, is that we default to creating .venv as the virtual environment. This needs to be improved to support multiple versions of python.

Ideally we will end up having a structure similar to the one below.

.
└── .venv
    ├── 3.7
    ├── 3.8
    └── 3.9

Concensus Required

• Directory structure and naming.
• Should we default to this behaviour or make it opt-in only?
• If we want to default to this behaviour, should we start by opt-in first, and then opt-out?
• How should existing environments be handled? We can detect this and set project level config.

Tasks

• Drive concensus, approved by members of @python-poetry/core
• Implement new structure
• Implement test cases that validate new environment creation(s), gracefull handling of existing environments, compatibility with existing env sub-commands.

Related issues: #2908

[finswimmer]

For sure @artorias111. We always appreciate contribution.

But we need to first come to a consensus on how it should look like, as @abn described in his post.

fin swimmer

[luismojena]

I don’t know if it’s on purpose, but I use this command export POETRY_VIRTUALENVS_PATH="$PWD/.venvs", and what @abn is proposing happens naturally