build(docker): add docker hub push capabilities

[d33bs]

Description

This PR continues the efforts surrounding #214 to push Docker images to Docker Hub using various triggers from GitHub Actions. I tried to abide the spec mentioned by @bethac07 (thanks Beth!) with slight adjustment to add the dynamic version to each tag along with the commit hash (which includes a commit hash for non-release-based versions). Please don't hesitate to let me know if I should change the tagging or other aspects to meet the goals here.

Open question I had while creating this: when would be best to create a scheduled push for Docker images? I chose Wednesdays as a time where challenges (if there were any) would be quite visible and could be resolved before week-end. I can also see how Mondays, Fridays, or sometime over the weekend would be good too.

Once this is merged, I believe we should see a new push triggered, and will likely be able to reach back out to Docker for more support surrounding their DSOS program.

Thank you in advance for any thoughts and suggestions you may have on this!

What is the nature of your change?

• Bug fix (fixes an issue).
• Enhancement (adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• This change requires a documentation update.

Checklist

Please ensure that all boxes are checked before indicating that a pull request is ready for review.

• I have read the CONTRIBUTING.md guidelines.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• New and existing unit tests pass locally with my changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have deleted all non-relevant text in this pull request template.

[kenibrewer]

Things are looking very clean, but there's a use of download_artifact I think will break and I have an additional suggestion around merging the docker "build-test" action and the "build-push" action into a unified "build-test-push" action.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.96%. Comparing base (9dd98ac) to head (7412759).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #377   +/-   ##
=======================================
  Coverage   94.96%   94.96%           
=======================================
  Files          56       56           
  Lines        3136     3137    +1     
=======================================
+ Hits         2978     2979    +1     
  Misses        158      158           

Flag	Coverage Δ
unittests	94.96% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[d33bs]

Thanks @gwaybio and @kenibrewer for your reviews! I've worked towards addressing these and believe things are now ready for a re-review when there's a moment.

[d33bs]

Hi @bethac07 and @kenibrewer , I've added some changes based on your comments and have re-requested your review. Please don't hesitate to let me know if I should make any further changes to help ready this for pycytominer.

[kenibrewer]

A few suggestions to make certain if checks a bit more restrictive. But otherwise this looks good to me and seems like implement's @bethac07 's tagging suggestions well.

Excited to see this merged so we can hotfix whatever github actions corner case we inevitably missed despite triple checking every line!

[bethac07]

I agree with Ken, I'm sure some hotfixing will be required just due to the laws of coding/the universe, but awesome job!

[d33bs]

Thank you so much @kenibrewer, @bethac07, and @gwaybio for your reviews and great suggestions throughout! Going to squash and merge this in.