Remove defer to handle new containerregistry limiter

[nicolasbender]

go-containerregistry introduces a limiter in the latest patch version which results in a deadlock when it needs to spawn more than 4 jobs. This enables bumping #165

[modulo11]

Is that behavior not more like a bug in the library and should be fixed there?

If we now explicitly call Close() we should check for its error.

[nicolasbender]

Is that behavior not more like a bug in the library and should be fixed there?

If we now explicitly call Close() we should check for its error.

We ignored the error already when we used defer, so I doubt this would change much. Regarding the library: This seems to be introduced as a safeguard and as an alternative, we could also increase the default job size. But this has the risk of failing again when the new limit is still too low

[nicolasbender]

Is that behavior not more like a bug in the library and should be fixed there?

You are probably right, we are also not the only one with this issue but the respective PR to fix it seems to be deleted? google/go-containerregistry#2277