Used trusted publishers for testpypi publishing

[natestemen]

Description

This PR fixes the failing testpypi publishing action which runs nightly to ensure Mitiq can be uploaded to PyPI.

In addition it adds a check to ensure the version uploaded to testpypi is what is then later downloaded.

resolves #2150

⚠️ before merging ⚠️:

• create an environment (through GitHub) called testpypi [docs]
• create an environment (through GitHub) called pypi (this will be done in a follow on PR when this change takes effect for the main release workflow)
• ensure testpypi is set up properly to accept trusted publishing [docs]

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.32%. Comparing base (e76ef08) to head (12b520f).
Report is 88 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2320      +/-   ##
==========================================
+ Coverage   98.29%   98.32%   +0.02%     
==========================================
  Files          90       87       -3     
  Lines        4274     4048     -226     
==========================================
- Hits         4201     3980     -221     
+ Misses         73       68       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[natestemen]

Reviewer Note: This change is still somewhat experimental and is hard to test thoroughly. We may want to merge these changes with the exception of 20aeef4 which adds trusted publishing for (main) PyPI. This way we can ensure TestPyPI uploads work correctly before adding it to the main upload process. Also if there are issues, it gives us time to fix things before the 0.38 release goes out this Friday (June 28, 2024).

[cosenal]

Reviewer Note: This change is still somewhat experimental and is hard to test thoroughly. We may want to merge these changes with the exception of 20aeef4 which adds trusted publishing for (main) PyPI. This way we can ensure TestPyPI uploads work correctly before adding it to the main upload process. Also if there are issues, it gives us time to fix things before the 0.38 release goes out this Friday (June 28, 2024).

How do you plan to exclude that commit? Are you going to create a separate PR?

[natestemen]

How do you plan to exclude that commit? Are you going to create a separate PR?

Easiest thing to do (IMO) would be to add a new commit that is the anti-diff of 20aeef4 (i.e. revert the commit), so that in a follow on PR the commit can be cherry-picked and applied.

[cosenal]

How do you plan to exclude that commit? Are you going to create a separate PR?

Easiest thing to do (IMO) would be to add a new commit that is the anti-diff of 20aeef4 (i.e. revert the commit), so that in a follow on PR the commit can be cherry-picked and applied.

OK, sounds good to me 👍

[cosenal]

@natestemen LGTM. Do you want to push the anti-diff commit before I approve?

[natestemen]

testpypi environment set up and testPyPI set up to know about this github action as a publisher. merging. will be tested tonight when this runs.