Update Docker Tag Logic

[alexnorell]

Description

Update the release logic to support the following cases:

• releases will also push to latest if the GitHub release is tagged as the latest release AND the version in version.py matches the tag of the release. The tag of the release is normalized to remove the leading v. If both of those aren't true, the container tag will be set to the tag of the github release.
• push to main will only tag an image as main. This will allow for a bleeding-edge build
• custom tag will prepend the version from version.py to the tag, and will ONLY allow pushing the custom tag
• Force push will only update the container tag that matches the value in version.py

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How has this change been tested, please provide a testcase or example of how you tested the change?

This has been tested on a separate repository to verify all this functionality works:

• Actions runs testing all the features

Any specific deployment considerations

Release will push to latest again. This will also allow us to enable main builds in the future if desired.

Docs

• Docs updated? What were the changes: