chore: update poetry to version 2

[ireneisdoomed]

✨ Context

Poetry 2.0 has been released with breaking changes that caused our tests to fail because the TOML wasn't following the new structure.
Changes are described here: https://python-poetry.org/blog/announcing-poetry-2.0.0

I've migrated the config to the new structure, interestingly you can now pin the Poetry version to use.

🛠 What does this PR implement

• Project TOML adherence to Poetry 2.0
• Poetry version pinned to 2.0
• Minor fixes in various places to deprecate using typing's modules

🙈 Missing

🚦 Before submitting

• Do these changes cover one single feature (one change at a time)?
• Did you read the contributor guideline?
• Did you make sure to update the documentation with your changes?
• Did you make sure there is no commented out code in this PR?
• Did you follow conventional commits standards in PR title and commit messages?
• Did you make sure the branch is up-to-date with the dev branch?
• Did you write any new necessary tests?
• Did you make sure the changes pass local tests (make test)?
• Did you make sure the changes pass pre-commit rules (e.g poetry run pre-commit run --all-files)?

[ireneisdoomed]

This PR is blocked because the deptry tests are failing. This tool checks that we don't use any dependency in the code that is not defined in the TOML.
They have an open PR to parse Poetry's new dependencies definition in the TOML fpgmaas/deptry#1003

Tests should pass once deptry is updated.

[project-defiant]

The packages and requres-poetry are not available at the project, by the looks of the documentation https://python-poetry.org/docs/pyproject/#packages and https://python-poetry.org/docs/pyproject/#requires-poetry

[ireneisdoomed]

I followed the structure in https://github.com/python-poetry/poetry/blob/main/pyproject.toml

I guess both ways are correct