Convert setup.py to pyproject.toml

[gforcada]

Use uvx --from plone.meta setup-to-pyproject to migrate setup.py configuration over to pyproject.toml leaving a single line on setup.py to keep it compatible with zc.buildout

[mister-roboto]

@gforcada thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

[mauritsvanrees]

This is mostly fine, but I added some suggestions.

[gforcada]

@mauritsvanrees I hope now is a good time to start the project to move metadata to pyproject.toml, Plone 6.2 is already out, we had already the first point release and things are stable enough to drive this.

As usual, I start with plone.batching 🙃

[mauritsvanrees]

The lines for the zcml autoinclude plugin are gone now. This was fixed in plone.meta meanwhile.

But: Products.CMFPlone explicitly loads the zcml of this package:

<include package="plone.batching" />

So I think this is totally fine. Probably for most plone.* packages this auto include plugin can be removed from setup.py/pyproject.toml. Well, those packages living below Products.CMFPlone anyway.