feat: build UBI-based image

[aboguszewski-sumo]

This is more like a PoC than ready PR:

• only linux/amd64 was added
• dev builds are only to confirm that it builds successfully: IMO we should only have this enabled for releases
• LATEST_TAG_FIPS_SUFFIX was used as a temporal solution: imo we should rename it just to LATEST_TAG_SUFFIX and use it as usual

[swiatekm-sumo]

dev builds are only to confirm that it builds successfully: IMO we should only have this enabled for releases

I disagree, anything we build for releases should also be built for dev. Otherwise we're never going to catch breakage.

The approach in this PR looks reasonable to me in general.

[sumo-drosiek]

* `LATEST_TAG_FIPS_SUFFIX` was used as a temporal solution: imo we should rename it just to `LATEST_TAG_SUFFIX` and use it as usual

Can we rename it in this PR, or another one and merge it before this PR?

[andrzej-stencel]

dev builds are only to confirm that it builds successfully: IMO we should only have this enabled for releases

I disagree, anything we build for releases should also be built for dev. Otherwise we're never going to catch breakage.

I agree we should build, but we probably don't need to push the non-release UBI images to an image repository, right?

[swiatekm-sumo]

dev builds are only to confirm that it builds successfully: IMO we should only have this enabled for releases

I disagree, anything we build for releases should also be built for dev. Otherwise we're never going to catch breakage.

I agree we should build, but we probably don't need to push the non-release UBI images to an image repository, right?

We currently do it for all builds on main, which I think is valid, as it makes it much easier to run external tests on dev versions.

[swiatekm-sumo]

LGTM, although we should add UBI FIPS images in a subsequent PR.