Pivot PyPI publishing to use trusted publishers

[mtreinish]

This commit updates the wheel job CI configuration to leverage PyPI's trusted publisher mechanism. Moving forward the bot account we've been using will be deleted (as it will require 2fa) and the rustworkx github repository's wheels.yml workflow has been setup as a trusted publisher. This commit updates the job configuration per:

https://docs.pypi.org/trusted-publishers/using-a-publisher/

to autheticate the job directly against pypi for publishing the package files without needign any user credentials.

[coveralls]

Pull Request Test Coverage Report for Build 6562574063

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 96.523%

---

Totals
Change from base Build 6540082471:	0.0%
Covered Lines:	15544
Relevant Lines:	16104

---

💛 - Coveralls

[IvanIsCoding]

LGTM but I think we should trigger it once before 0.14 to publish the current state to TestPyPI. Apparently it's not very hard:

repository-url: https://test.pypi.org/legacy/

[mtreinish]

It's a good thing you asked me to test this, I just setup my fork to push to test.pypi.org and it failed because the publish action only works on linux: https://github.com/mtreinish/retworkx/actions/runs/6538918751/job/17755862386#step:8:1

This is actually documented see: https://github.com/pypa/gh-action-pypi-publish#non-goals I'll adjust the job to work with this and then retest.

[mtreinish]

Aside from the issue on non-linux runners, the trusted publisher upload works as expected to test pypyi:

• https://github.com/mtreinish/retworkx/actions/runs/6538918751/job/17755862004#step:9:1
• https://test.pypi.org/project/rustworkx/#files

[IvanIsCoding]

It's a good thing you asked me to test this, I just setup my fork to push to test.pypi.org and it failed because the publish action only works on linux: https://github.com/mtreinish/retworkx/actions/runs/6538918751/job/17755862386#step:8:1

This is actually documented see: https://github.com/pypa/gh-action-pypi-publish#non-goals I'll adjust the job to work with this and then retest.

An unfortunate surprise but I am glad we caught it. Upload artifacts seems like extra steps but I don’t think they’ll add Windows/mac support ever by the wording of their documentation

[mtreinish]

Ok, I've updated the job definition in: 781014a to use a a shared upload stage. Then I pushed another test to my fork branch on test pypi here: mtreinish@284e055
and it is working as expecting:

https://github.com/mtreinish/retworkx/actions/runs/6552138251
https://test.pypi.org/project/rustworkx/0.14.1/#files (I bumped the version number to avoid file conflicts)

(the retworkx job failure is because I didn't bother configuring the trusted publisher pipeline for test pypi on retworkx)

[IvanIsCoding]

LGTM