Update RKE2 Images When New BCI is Available

[briandowns]

We need to automate the process of tagging new imagine in the image-build-* repositories whenever a new BCI image is available.

[tashima42]

I'm thinking about creating a new GitHub action to run every day and check if there are new images available and if there are, create releases.

[tashima42]

@briandowns In what repos exactly do we need to do this?

[briandowns]

image-build-dns-nodecache
image-build-k8s-metrics-server
image-build-sriov-cni
image-build-ib-sriov-cni
image-build-sriov-network-device-plugin
image-build-sriov-network-resources-injector image-build-calico image-build-cni-plugins
image-build-whereabouts
image-build-calico
image-build-flannel
image-build-etcd
image-build-containerd
image-build-runc
image-build-multus
image-build-rke2-cloud-provider

[tashima42]

I'm enumerating the steps that we need to do manually:

1. New bci image is released at: https://registry.suse.com/bci/golang121/index.html
2. Tag a new release at: https://github.com/rancher/image-build-base/releases and wait for the CI to run
3. Go to each image-build repo and update the .drone.yaml with the new tag
4. Tag a release with the same version as before, but a new date.

[briandowns]

We use the upstream Go images. BCI images are used for the components in RKE2 so those are the repos that will need to have new releases created.

[tashima42]

This is paused currently, we'll need to think of a way to ensure what exact go version to update the images to.

[tashima42]

Since I couldn't find a reliable way of deciding which version to update to, I'm going to update it to be manually set using an argument