Release workflow: Atomic PyPI pushing?

[onerandomusername]

As of now, each individual wheel is pushed to PyPI seperately. This means if CI fails on whatever wheel when making a PyPI release, the release will be incomplete.

These should follow best practices and construct all of the wheels to artifacts, before downloading the whole bunch and pushing to pypi in one swoop.

Ideally, this should also be gated with docker publish (but not build) and any other release artifacts that are created, in order to make sure releases are fully atomic.

half reference: #4611 and I am willing to implement this if that issue has gone stale

[motalib-code]

Give me assistance, as I am interested in solving this issue and having the participants resolve the problem. @amyreese