automate pushing kicbase image from snapshot to stable after release

[medyagh]

before release each time we build the kic base image we add the snashotX to it
for example
https://github.com/medyagh/minikube/blob/32922f4184c31fb405fb8dab7a1d7a8ef120b47a/pkg/drivers/kic/types.go#L27
Version = "v0.0.13-snapshot1"

this is good for when multiple people make corrections before a release, and once it is finalized, before the release we do this

docker tag kicbase/stable:v0.0.13-snapshot1 kicbase/stable:v0.0.13
docker tag kicbase/stable:v0.0.13 gcr.io/k8s-minikube/kicbase:v0.0.13
docker tag kicbase/stable:v0.0.13 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.13
docker push kicbase/stable:v0.0.13
docker push gcr.io/k8s-minikube/kicbase:v0.0.13
docker push docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.13

and change the types.go in kic package
https://github.com/medyagh/minikube/blob/32922f4184c31fb405fb8dab7a1d7a8ef120b47a/pkg/drivers/kic/types.go#L27

[prezha]

/assign

[prezha]

@medyagh i've created pr (#9439) to automate pushing kicbase image, please have a look

a few notes:

• there are some env vars required for passing credentials (details are in code comments)
• "GitHub Packages Docker registry will be superseded by GitHub Container Registry." (ref) - maybe we should plan to migrate in (near) future
• this pr does not cover updating corresponding Version in types.go in kic package atm - reason: open questions & proposal:

1. out of the three registries, what is/are minimally acceptable combination(s) of successful/failed updates - ie, which we would accept to fail and still update Version in pkg/drivers/kic/types.go? eg, just gcr is enough, or, at least gcr and one another, or, all three must be updated, etc.
2. when we (locally) update the Version in types.go, wouldn't we also want a pr to be automatically created (if one doesn't exist already)? that would also allow it to run as a standalone script
   if so, we could nicely combine this with eg, issue update go version to be 1.15 in go mod #9264 (i have improved version) with the approach proposed in issue Write a script to automatically propose PR's due to a new Kubernetes release #4392 (pr update_kubernetes_version: standalone script v2 #9384) and potentially any other issue that needs versions or any other value(s) updated in file(s)
   here, i would send out a complete proposal, just waiting to first agree on the proposed approach in issue Write a script to automatically propose PR's due to a new Kubernetes release #4392 (pr update_kubernetes_version: standalone script v2 #9384) and confirmation that the existing pr Upgrade go version to 1.15.2 #9280 is correct

please share your thoughts

[prezha]

@medyagh i've assumed that:

1. it would be acceptable to have at least one registry updated (that can be easily changed if needed), and so
2. i've included the updating corresponding Version in types.go in kic package, as well as automatically creating respective (unique) pr, as part of pr Add hack/update package to automate PR generation #9464

so this issue should be covered now