New package: hatch-1.2.1

[jcgruenhage]

Testing the changes

• I tested the changes in this PR: briefly

Bikeshedding opportunities

• As they aren't just libraries, but also CLI tools, do hatch/hatchling need the python3- prefix? I personally don't like it, and would argue in favor of removing it. Considering no one commented on this bit, I've decided to just get rid of.
• There's nearly no testing happening here, but that's due to the deps either requiring git checkouts with submodules, or themselves to be installed for testing. Any opinions on this? I'd prefer to have some amount of automatic testing here and not just a "JC has run this on his laptop once", considering that these are likely to be fairly central Python packages there are a few tests failing now, but they are being run and there's a hundred times more tests that do work as intended. The ones failing where it's expecting to be running /usr/bin/python, but is actually running /usr/bin/python3 or similar things, which is fine IMO.
• Is a major update of python3-click something that might need additional testing? 29 of our packages depend on it, but on the other hand, it's probably fine, right? Has been updated outside of this PR.

Fixes #37334

[icp1994]

Hello, I didn't know you were working on this already. I have been trying to package this for a few days and finally managed to get a working build. Since you have this PR already, please feel free to reuse any part of my commit if you wish.

[leahneukirchen]

Please rebase.