Container Images: Tag new patch releases with base minor release

[sarg3nt]

Is your feature request related to a problem? Please describe. Not a problem per say but a quality of life issue with our automation.

We'd like to float on patch releases of Kairos but can't because patch releases are not tagged with the minor release.

Example: We must specify v2.3.0_rockylinux when we'd like to use v2.3_rockylinux that would be tagged to the latest patch version. This is a fairly common practice in containerland.

Describe the solution you'd like v2.3_rockylinux is a tag of v2.3.0_rockylinux and when 2.3.1 is released then v2.3_rockylinux is retagged to v2.3.1_rockylinux

Describe alternatives you've considered Where possible we are using the github API to find the latest release and use that but this can be brittle and creates a failure point in our CD pipelines.

Additional context Specifically we need it for the framework:
quay.artifactory.metro.ad.selinc.com/kairos/framework:v2.3.0_rockylinux
as we are building our own core image, i.e.:

# https://github.com/kairos-io/kairos/releases
ARG KAIROS_VERSION="v2.3.0_rockylinux"

# https://quay.io/repository/kairos/framework?tab=tags&tag=latest
FROM quay.io/kairos/framework:$KAIROS_VERSION as kairos-framework

I'm about to start on our CD pipeline and can automate this there by calling the Github API but it would reduce my code and failure points if the tags existed.