Fix the MinIO image cache key in the kind e2e workflow (#10631)

* Fix the MinIO image cache key in the kind e2e workflow

The build job restores the MinIO image with
minio-bitnami-${{ env.BITNAMI_CONTAINERS_COMMIT }} and the e2e jobs look
for the same key, but the save step writes
minio-bitnami-${{ steps.minio-version.outputs.dockerfile_sha }}. No step
has that id, so the expression is empty and the image is saved under a
key nothing ever reads.

Upstream only works because an entry under the right key is still in the
cache and kept alive by use; caches unused for seven days are evicted, so
a quiet week would leave every e2e job unable to load the image. A fork
has no such entry, so all of them fail at once:

  Loading MinIO image...
  ./minio-image.tar: No such file or directory

Save under the key the restores ask for.

Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>

* Add changelog for #10631

Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>

---------

Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>

.github/workflows/e2e-test-kind.yaml

@@ -105,7 +105,7 @@ jobs:
         uses: actions/cache/save@v6
         with:
           path: ./minio-image.tar
-          key: minio-bitnami-${{ steps.minio-version.outputs.dockerfile_sha }}
+          key: minio-bitnami-${{ env.BITNAMI_CONTAINERS_COMMIT }}
   # Create json of k8s versions to test
   # from guide: https://stackoverflow.com/a/65094398/4590470
   setup-test-matrix:

changelogs/unreleased/10631-krishhna24

@@ -0,0 +1 @@
+Fix the MinIO image cache key in the kind e2e workflow so the cached image is found