CI: runner tag for Docker image production in registry.h.n
As mentioned in the comments of #91, we have problems most likely induced by the S3 cache for jobs that attempt to push Docker images to registry.heptapod.net using Kaniko.
I expect other kind of build/push tools to be affected as well.
The simplest course of action could be to create dedicated runners for such purpose, which would not be hosted on servers with the S3 cache (we currently have two of them).
Namely, we'd have a
container-registry-push tag. Jobs for Docker image production would need to mention it in their configuration