chore(deps): migrate containers/image/v5 to go.podman.io/image/v5

[frewilhelm]

What this PR does / why we need it

containers/image/v5 moved to a monorepo and our now available from go.podman.io/image/v5

Which issue(s) this PR is related to

test are failing

[frewilhelm]

ocm.software/ocm@v0.39.0 still depends on the old github.com/containers/image/v5 and github.com/containers/storage module paths. Since our direct dependency go.podman.io/image/v5 pulls in go.podman.io/storage, the dependency graph ends up with two copies of the storage module under different paths — both containing the same unshare.c. On Linux, the linker sees the duplicate _containers_unshare symbol and fails.

ocm.software/ocm@v0.40.0-rc.1 has migrated to go.podman.io/image/v5 and go.podman.io/storage. With every dependency now using the new module paths, the old github.com/containers/image/v5 and github.com/containers/storage drop out of the graph entirely. One module path, one copy of the C code, no linker conflict.

Thats why it worked with ee65934

I will revert this and we will wait until ocm 0.40.0 is available