CI Production Workflows for Docker and Docs

[SteveDMurphy]

Closes #807

Code Changes

• Add a conditional step to check if the tag used matches a release
• Include the current image when pushing a production image
• Parse the github.event.ref to publish the version specific docs
• Mimic the conditional step for docs publishing

Steps to Confirm

• Set up a testing repo to ensure the workflow worked
• Add a test nox command to print out the update IMAGE constant with version

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation Updated:
  • documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
  • documentation issue created (tag docs-team to complete issue separately)
• Issue Requirements are Met
• Relevant Follow-Up Issues Created
• Update CHANGELOG.md

Description Of Changes

Spent some time in a test repo to ensure the workflow updates should work for us.

I'm unsure still if the nox changes are sufficient, or if there should be a separate constant used for the current working version.

Another additional question is if we want to retroactively publish docs versions that were missed 🤔

[earmenda]

nice

[ThomasLaPiana]

That's pretty cool, good solution :D

[ThomasLaPiana]

@SteveDMurphy I don't feel a need to publish old docs versions, I think it'll be good enough to have going forward but not worth back-filling