ci: cloud provider releases

[ghost]

Resolves #12367
Related Issue: PrefectHQ/prefect-operator#30

Validation

Most testing was performed through running successfully pre-releases and releases on a pull request opened again a forked repository. Commits were then cherry-picked into another feature branch prefixed with forked/ to avoid introducing a series of hacks which were required to force the github workflows to correctly publish to my personal docker registry.

Release Evidence

• https://hub.docker.com/repository/docker/josephmcasey/prefect/general
• https://hub.docker.com/repository/docker/josephmcasey/prefect-client/general
• https://hub.docker.com/repository/docker/josephmcasey/prefect-dev/general
• https://hub.docker.com/repository/docker/josephmcasey/prefect-client-dev/general

Topics of Discussion

• What sort of automated testing, if any, on github workflows would be desired for this feature request to be meet maintenance standards for PrefectHQ?

Checklist

• Review contribution guidelines: https://docs.prefect.io/contribute/index
  • Not very much documentation on contributing to developer operation automation
• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• If this pull request adds new functionality, it includes unit tests that cover the changes
• If this pull request removes docs files, it includes redirect settings in mint.json.
• If this pull request adds functions or classes, it includes helpful docstrings.

[github-actions]

This pull request is stale because it has been open 14 days with no activity. To keep this pull request open remove stale label or comment.

[zzstoatzz]

hi @josephmcasey - we'll keep this in mind, but I think we'll hold off on this for now. this will non-trivially increase CI runtime. in the meantime, you can build a custom image based on our image images