Switch to PEP 517 packaging using hatchling

[akx]

Pull Request check-list

Please make sure to review and check all of these items:

• Does $ tox pass with this change (including linting)?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?
  • not applicable
• Was the change added to CHANGES file?
  • not yet

Description of change

This PR shifts redis-py from legacy setup.py packaging to PEP 517 compliant packaging using hatchling from PyPA.

Essentially, this does what was discussed in #1658 but with the increasingly standard hatchling tool instead of poetry's idiosyncracies.

Refs #1316 (which initially did this, with tools from that age)
Refs #1649 (which reverted that for no good reason)

I wasn't able to test all of these changes yet, but python -m build does create a working wheel with all modules included.

[chayim]

With no clear winner in the packaging space (yet) - and the ongoing flux, I don't see redis-py moving from setup.py currently. As this changes, it too should change. But hatch, is yet another attempt at something, and we'll watch it as it gains steam.

[ofek]

I don't see redis-py moving from setup.py currently.

Hey! Do you have some heuristic in mind, so the next person doesn't waste their time?

the ongoing flux

I don't see much of that. The pyproject.toml way is for sure the standard, is documented as such, and the execution of setup.py files is deprecated.

[ischaojie]

sadly to see this :(, pyproject.toml is already the de facto standard.