Update gcr.io/gcp-runtimes/container-structure-test with new releases

[retornam]

@loosebazooka @thesayyn @spowelljr

The latest image on the gcr.io/gcp-runtimes/container-structure-test image registry is v1.16.0 but the latest release on this project's releases page is v1.19.3

Would it be possible to update the image registry automatically whenever a new release is cut? It would really help streamline our workflow and ensure consistency across deployments. Thanks so much!

Thank you.

➜ gcrane ls --json gcr.io/gcp-runtimes/container-structure-test | jq  '.tags[]' | sort  --version-sort
"1a6f81542c538402cd8e7ae99ad1a187491aba0e"
"1a24a6b665dc45c0690ca2e664d605297986611a"
"1b466df7f1289ec7172ba4692776f78fd08a67e7"
"01fed1935fb516d5af4ad60254ad01617e886f83"
"1.5.0"
.... snipped
"infrastructure-public-image-fe27758bb05d46750f1e7ae0d351d0eb832644b8a5ed9e6e063918460d68c05a"
"latest"
"v0.1.1"
"v0.1.2"
"v0.1.3"
"v0.2.0"
"v0.2.1"
"v0.3.0"
"v1.0.0"
"v1.1.0"
"v1.2.0"
"v1.2.1"
"v1.2.2"
"v1.3.0"
"v1.4.0"
"v1.5.0"
"v1.6.0"
"v1.8.0"
"v1.9.0"
"v1.9.1"
"v1.10.0"
"v1.11.0"
"v1.12.0"
"v1.13.0"
"v1.14.0"
"v1.15.0"
"v1.16.0"

[loosebazooka]

I think it would be unlikely. We do publish container images to ghcr.io for this project though, see releases. The docs probably need an update