Make tool available as wheel

[jensens]

IOW: requiring docker sucks ;)

[gforcada]

Maybe rather than, yet-another-tool-orchestrator, we might follow the lead of the zopefoundation organization and replicate https://github.com/zopefoundation/meta but for plone.

We could start with:

• black
• isort
• pyroma

And once that's stable and running, keep expanding it with pyupgrade and plenty of other linters and formatters that we, as Plone community, agree on.

What I like about zopefoundation/meta is that the configuration is central on that repository (so you get a single source of truth ✨ ), but you get the option to override on a per repository basis (like, you could decide that py3+ only packages can run pyupgrade --py38-plus while on packages that still have to keep py2 compatibility they are avoided.

Plus, given that the configuration is central on the meta repository, you don't have to keep adding tool-specific configuration files, but rather you can use each tool own configuration files, i.e. .isort.cfg of pyproject.toml or setup.cfg etc, but without custom keys.

This allows to run the tools locally with the very same settings they will run on CI, otherwise, one can run black/isort/flake8 locally, get the code formatted, and then CI complain because of a version/configuration mismatch 💥

There's nothing more frustrating than contributing a PR to an open source project and have to fight a CI to get your ✅ on the CI jobs.

Maybe I should write this on community.plone.org post? 😅