Python version dependencies are not correctly handled on VOLTTRON startup.

[davidraker]

Describe the bug
VOLTTRON attempts to create a pyproject.toml file on startup, and will crash if any packages in the python environment are misaligned with volttron's version dependency. Additionally, poetry always seems to believe volttron has a dependency on python>=3.10,<3.11, even though the pyproject.tomls all seem to list python>=3.10,<4.0.

To Reproduce
Steps to reproduce the behavior:

1. Install volttron and a package which has a dependency on python 3.11 or greater:
   $ pip install volttron
   $ pip install matplotlib

2. Start volttron. Observe the error (after a minute or so).
   $ volttron -vv
   ...a minute or so of logs....
   RuntimeError: Unable to update pyproject.toml in /home/vuzer/.volttron with venv's current list of libs. ('Error from poetry command:', '\nThe current project's supported Python range (>=3.10,<3.11) is not compatible with some of the required packages Python requirement:\n - contourpy requires Python >=3.11, so it will not be installable for Python >=3.10,<3.11\n\nBecause volttron depends on contourpy (1.3.3) which requires Python >=3.11, version solving failed.\n\n * Check your dependencies Python requirement: The Python requirement can be specified via the python or markers properties\n\n For contourpy, a possible solution would be to set the python property to ""\n\n https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,\n https://python-poetry.org/docs/dependency-specification/#using-environment-markers\n\n'))

3. Note that the pyproject.toml file was created, but does not include all packages in the python environment:
   $ cat .volttron/pyproject.toml

4. Start volttron a second time. Observe that there are no errors because the (incomplete) pyproject.toml file already exists.

Expected behavior

• VOLTTRON should never have a dependency of python <3.11.
• The incomplete pyproject.toml should not be left in the VOLTTRON_HOME
• VOLTTRON should start even if there are incompatible packages in the environment. They may be irrelevant to VOLTTRON.
• If possible, in cases where there is a real conflict, VOLTTRON should provide meaningful output that indicates where the conflict has arisen.

[schandrika]

poetry will not add packages that require python version greater than the minimum python version supported by volttron. it does not check against just the version of current python version. For example, if current virtual environment contains packageA that depends on packageB which requires python >=3.11, when volttron creates a poetry environment, and does a "poetry add packageA" the statement will volttron supports 3.10 and up but packageB only support python 3.11 and above. Poetry does that to ensure that a project with all its dependency can run on all supported python environments. Based on testing and developer discussion the solution proposed is:

1. On start of VOLTTRON, when creating a poetry environment inside volttron home, make that poetry project(i.e. vhome/pyproject.toml) to only use the current python version after checking if the current version is within the bounds of supported versions. For example, if volttron-core's toml file specifies python range as >=3.10, <4, and current version of python is 3.11 create vhome/pyproject.toml with python requirement as ~3.11.0. This would avoid lot of version issues for downstream packages. Many downstream packages have markers such as "use version x if python_version<=n and user version y if python_version>n" such marker would automatically get applied for the single version of python specified in vhome/pyproject.toml

2. On start if current version of python is not within range specified in volttron-core, raise exception

3. if vhome/pyproject.toml already exists and the current version of python is different from what is in vhome/pyproject.toml, even if the version is within the range supported by volttron-core, raise exception and ask user to point to new vhome or delete
   vhome/pyproject.toml so that current vhome's poetry project can be recreated.

4. in case of any exception, any partial vhome/pyproject.toml should be removed