Dependency version issues

[LukeVader-IV]

i want to test this tool on my local machine before attempting to deploy it.
when following installation instructions at the bottom of the main README page, i get the following

$ poetry install -E fileobjects -E openioc -E virustotal -E email -E url
The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Creating virtualenv mail2misp-XwM6Wlws-py3.12 in /var/home/$USER/.cache/pypoetry/virtualenvs
Installing dependencies from lock file

pyproject.toml changed significantly since poetry.lock was last generated. Run `poetry lock` to fix the lock file.

so, as the output reccomends, i run the command

$ poetry lock
The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (7.1s)The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (8.5s)The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (9.3s)The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (10.3s)The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (11.1s)The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (13.9s)The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (15.6s)The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (20.2s)The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.
Resolving dependencies... (23.3s)

The current project's supported Python range (>=3.8.1,<3.9) is not compatible with some of the required packages Python requirement:
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9
  - o365 requires Python >=3.9, so it will not be installable for Python >=3.8.1,<3.9

Because no versions of o365 match >2.0.31,<2.0.32 || >2.0.32,<2.0.33 || >2.0.33,<2.0.34 || >2.0.34,<2.0.35 || >2.0.35,<2.0.36 || >2.0.36,<2.0.37 || >2.0.37,<2.0.38 || >2.0.38,<2.1.0 || >2.1.0,<2.1.1 || >2.1.1,<2.1.2 || >2.1.2,<3.0.0
 and o365[o365] (2.0.31) requires Python >=3.9, o365 is forbidden.
And because o365[o365] (2.0.32) requires Python >=3.9, o365 is forbidden.
And because o365[o365] (2.0.33) requires Python >=3.9
 and o365[o365] (2.0.34) requires Python >=3.9, o365 is forbidden.
And because o365[o365] (2.0.35) requires Python >=3.9
 and o365[o365] (2.0.36) requires Python >=3.9, o365 is forbidden.
And because o365[o365] (2.0.37) requires Python >=3.9
 and o365[o365] (2.0.38) requires Python >=3.9, o365 is forbidden.
And because o365[o365] (2.1.0) requires Python >=3.9
 and o365[o365] (2.1.1) requires Python >=3.9, o365 is forbidden.
So, because o365[o365] (2.1.2) requires Python >=3.9
 and mail2misp depends on O365[o365] (^2.0.31), version solving failed.

  * Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties

    For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"
For o365, a possible solution would be to set the `python` property to "<empty>"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers