Recent IoT composes include a couple of container images - bootc and bootc-tier0. We should support publishing these.

Per @pbrobinson they're currently using yet another bash script forked from sync-latest-container-base-image.sh to do this. We should support it here to snip this terrifying and potentially universe-threatening proliferation of bash scripts in the bud.

It's not entirely clear how the bootc-tier0 container is going to be published, AFAICS, so for now I think we'll ignore it and just publish the bootc one.

They did add an interesting check to the script - here - which aborts the publication if all expected arches didn't succeed. This is an interesting wrinkle I hadn't thought about in the switch from Koji-based to compose-based publishing; when the Koji-based script run it would always find the last successful image, so as long as there had been one successful build for the relevant container, arch and release, it'd have something to publish, even if it was old. But with compose-based publishing, I guess we run the risk of "erasing" an arch from the registry if it doesn't succeed in a compose, at least when referenced as e.g. fedora:40 or fedora:latest. I guess I'll file a separate ticket about that.