Bump up github.com/docker/docker to v25.0.6 version.

[thepetk]

Which area is this issue related to?

/area library
/area registry
/area test-automation

Issue Description

The following repos need to be updated and their modules should use github.com/docker/docker version v25.0.6

devfile/library

• library: Suggested fix is Bump github.com/docker/docker from 25.0.1+incompatible to 25.0.6+incompatible library#221
• library: Cut a new release for library.

devfile/registry

• tests/odov3: chore(deps): bump github.com/docker/docker from 25.0.1+incompatible to 25.0.6+incompatible in /tests/odov3 registry#461 has been opened to address the issue.
• tests/validate_devfile_schema: library fix needs to be merged first & then we should bump up its dependency.
• tests/odov3 library bumped

devfile/registry-support

• tests/integration: Suggested fix is Bump github.com/docker/docker from 25.0.1+incompatible to 25.0.6+incompatible registry-support#251
• index/generator: library fix needs to be merged first & then we should bump up its dependency
• index/server: library fix needs to be merged first & then we should bump up its dependency
• registry-library: The registry-generator fix needs to be merged first & then we should bump up its dependency

devfile/registry-operator

• Fix is suggested here: Bump github.com/docker/docker from 25.0.1+incompatible to 25.0.6+incompatible registry-operator#93
• Bump registry-library dependency after it is merged: https://github.com/devfile/registry-operator/blob/main/go.mod#L7

Acceptance Criteria

• All modules in library, registry, registry-support & registry-operator are using github.com/docker/docker v25.0.6

[Jdubrick]

Since the dependency bump is a critical severity we should be cutting new releases for affected items, I can cut a new library release so we can pull that dependency into most of the action items

[Jdubrick]

Added action item to registry-operator to bump up the registry-library hash to pull in the fix as well: https://github.com/devfile/registry-operator/blob/main/go.mod#L7

[thepetk]

Since the dependency bump is a critical severity we should be cutting new releases for affected items, I can cut a new library release so we can pull that dependency into most of the action items

+1 for the new release. Initially I thought only updating the hash but it feels much cleaner. I've updated the criteria to include this action. As you're now the assignee feel free to update them as you see fit <3

[thepetk]

blocks #1605