fix: update redis image reference to use proper docker io location

[Skarlso]

On-behalf-of: Gergely Brautigam gergely.brautigam@sap.com

What this PR does / why we need it

Fixes open-component-model/ocm-project#974

Which issue(s) this PR is related to

[frewilhelm]

any idea why it stopped working?

[Skarlso]

@frewilhelm It's a hunch right now. :D There was a change in docker hub that looks like it's affecting some things with regards to how it resolves access. Let's see if this works or not. :)

[Skarlso]

    main_test.go:110: failed to modify component version: cannot determine digest: oci artifact "failed to resolve manifest "docker.io/library/redis:6.0.1": HEAD "https://registry-1.docker.io/v2/library/redis/manifests/6.0.1": GET "https://auth.docker.io/token?scope=repository%3Alibrary%2Fredis%3Apull&service=registry.docker.io": response status code 403: Forbidden" is unknown

Nope. :)

[Skarlso]

Ah... it is that.... docker hub old version is no longer accessible. Just need to update the version to latest.

Because of their licensing changes.

Hmmm... nope.

[Skarlso]

Ah I found it. I'll try to implement a fix.

[Skarlso]

FUCK! The signing and verification also wants/needs access and I don't want to set up an ocmconfig with tokens and credentials and whatnot. I will just rip out redis from podinfo.

[Skarlso]

Okay, done. Podinfo will no longer deploy and need redis.