The image pull functionality is currently duplicated across multiple areas:

1. operator-controller internal (shared by op-con and catd controllers)
2. operator-registry (used by opm render, opm migrate)
3. new tests for catalogs under operator-controller implemented in OPRUN-3810

These implementations are likely subtly different, leading to maintenance issues and churn. To centralise this functionality and ensure consistency, we should create a dedicated upstream library, potentially named `operator-framework/image-utils`. All existing components will use this new library, eliminating code duplication and simplifying future updates and fixes.