Compatibility with poetry 2.0

[dbIgel]

Describe the bug
Poetry 2.0 changed the hash format (again), it re-packs the data when configured in the new pyproject.toml format, see code and announcement

To Reproduce
Steps to reproduce the behavior:

1. Use poetry 2 to generate the poetry.lock
2. Run micropipenv.py verify
3. Its not valid

Expected behavior
A clear and concise description of what you expected to happen.

The _compute_poetry_hash funciton should be extended, as done for #280 to support the new format

Screenshots
-

Additional context
-

[frenzymadness]

Thank you very much for the detailed report. It seems you know all the details and what has to be done. Would you consider opening a PR?

[dbIgel]

Thats just what i found out while having a quick look at the code :D
Some patching around was somewhat successful but didn't show the expected results so i would propose to more or less adapt the poetry logic directly instead of "patching around" it.

[dbIgel]

@frenzymadness i created #313 as a start which adds support for the new format during validation, feel free to have a look at it and suggest anything that i have missed, tests to be added etc.