🌱 Upgrade github.com/operator-framework/operator-registry from 1.51.0 to 1.52.0

[camilamacedo86]

Description of the change:

Motivation for the change:

Architectural changes:

Testing remarks:

Reviewer Checklist

• Implementation matches the proposed design, or proposal is updated to match implementation
• Sufficient unit test coverage
• Sufficient end-to-end test coverage
• Bug fixes are accompanied by regression test(s)
• e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• Docs updated or added to /doc
• Commit messages sensible and descriptive
• Tests marked as [FLAKE] are truly flaky and have an issue
• Code is properly formatted

[camilamacedo86]

@grokspawn @tmshort
The operator-registry requires 1.23.7

[camilamacedo86]

@grokspawn @tmshort
The operator-registry requires 1.23.7

[tmshort]

/hold

[tmshort]

For reasons, we can't update golang to 1.23.7.
I do wonder, if perhaps, on operator-registry, we require an older version of distribution/distribution/v3 and use a replace to get the latest? That way, maybe we can stick with golang 1.23.6? Not sure how that works when we pull it in, however.

[camilamacedo86]

Clsoed in favor of " #3562