Use `poetry-core` build backend rather `poetry` to reduce build dependencies

[codedawi]

Poetry recommends using poetry-core and specifically poetry.core.masonry.api as the build backend to reduce dependencies required for building package. See poetry documentation: https://python-poetry.org/docs/pyproject/#poetry-and-pep-517.

[build-system]
-requires = ["poetry>=0.12"]
-build-backend = "poetry.masonry.api"
+requires = ["poetry-core"]
+build-backend = "poetry.core.masonry.api"

Please note functionality will not change as poetry.masonry.api simply imports peotry.core.masonry.api methods.

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[g-as]

See #2199

[Secrus]

Just FYI, it is recommended to migrate to poetry-core as the backend, since poetry doesn't expose build hooks for editable builds (unless using Poetry itself).