Fix for modern poetry

[lemenkov]

Description

Poetry 2.0+ requires a different pyproject.toml layout.

Fixes #25.

Customer Impact (optional)

Users can use modern Poetry.

Performance Impact (optional)

N/a. Deployment-time issue.

How Has This Been Tested?

Tried poetry check.

Software Configuration(s): (optional)

• Operating System: any
• Software version: 0.2.7
• Branch: any
• Toolchain version: n/a
• SDK version: n/a

Reviews

Please identify two developers to review this change

• @skellet0r
• @charles-cooper

Checklist: (Please delete options that are not relevant)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[charles-cooper]

i can't actually reproduce the error that was reported. i have poetry 2.1.1:

$ poetry --version
Poetry (version 2.1.1)

i do see some warnings were fixed in this branch compared to master. but there are still some warnings remaining:

Warning: [tool.poetry.extras] is deprecated. Use [project.optional-dependencies] instead.
Warning: [tool.poetry.dependencies] is set but [project.dependencies] is not and 'dependencies' is not in [project.dynamic]. You should either migrate [tool.poetry.depencencies] to [project.dependencies] (if you do not need Poetry-specific features) or add [project.dependencies] in addition to [tool.poetry.dependencies] or add 'dependencies' to [project.dynamic].
Warning: [tool.poetry.dependencies.python] is set but [project.requires-python] is not set and 'requires-python' is not in [project.dynamic].