Virtual environments should include python patch version

• [x ] I have searched the issues of this repo and believe that this is not a duplicate.
• [ x] I have searched the documentation and believe that my question is not covered.

Feature Request

I think this is somewhat related to #2282 but perhaps framed differently

I am using pyenv with poetry. It looks like poetry creates/uses virtual environments strictly based on the python major version.
eg it will distinguish between 3.7 vs 3.8 but not between 3.8.2 vs 3.8.3
This makes switching between two different minor versions of python difficult.

pyenv shell 3.7.8
poetry env info # displays virtual env created with python 3.7.8
pyenv shell 3.8.2
poetry env info  # displays virtual env created with python 3.8.2
pyenv shell 3.8.3
poetry env info  # still displays python 3.8.2 virtual env

It is not difficult to work around this using pyenv virtualenv and disabling poetry's virtualenv handling.
However, I think it makes more sense for poetry to include the minor version when determining the virtual environment.

Start by reproducing the pyenv and poetry env info sequence described in the issue with Python 3.8.2 and 3.8.3. Trace how Poetry selects virtual environments, then verify that changing the Python patch version selects a distinct environment while existing major-version behavior remains intact.