Refactor GitHub Actions

[prryplatypus]

• Simplifies all Tox actions by using a simple-tox action that does all the initial test setup transparently.
• Merges all PR actions into a single pr-tests.yml file
• Improves release flow merging PyPi and Docker release flow into publish-release.yml:
  • Package version gets injected into the package automatically when publishing to PyPi
  • Docker images get built after package is pushed to PyPi with the following tags (using Python 3.9 as an example):
    • 3.9-latest if the "Set as the latest release" checkbox is marked when creating a release
    • 3.9-YY.MM every time
    • 3.9-LTS if the release MM is 12

[prryplatypus]

Actions are failing because of #2807

[ahopkins]

One thing I've also been thinking about doing is dropping codecov for a number of reasons, and simplifying to just use the coverage.py results. CI can create the HTML results and stash them as an artifact to display with maybe posting back a comment on the PR. WDYT?

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +0.028% 🎉

Comparison is base (31d1470) 88.783% compared to head (7046b8c) 88.811%.

Additional details and impacted files

@@              Coverage Diff              @@
##              main     #2808       +/-   ##
=============================================
+ Coverage   88.783%   88.811%   +0.028%     
=============================================
  Files           92        92               
  Lines         7052      7070       +18     
  Branches      1197      1212       +15     
=============================================
+ Hits          6261      6279       +18     
- Misses         542       544        +2     
+ Partials       249       247        -2     

see 13 files with indirect coverage changes

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

[prryplatypus]

One thing I've also been thinking about doing is dropping codecov for a number of reasons, and simplifying to just use the coverage.py results. CI can create the HTML results and stash them as an artifact to display with maybe posting back a comment on the PR. WDYT?

Could look into it, but I don't think it's possible to attach artifacts to a PR directly. However, maybe for a future PR?

[ChihweiLHBird]

This refactor looks so great! Thanks for the effort!

[ChihweiLHBird]

Looks good to me! But I think it would be nicer if we can test the release in a fork of the repo.

[prryplatypus]

Looks good to me! But I think it would be nicer if we can test the release in a fork of the repo.

We did! There's a bunch of test releases in test pypi.org and in my Docker account (prryplatypus). :)