Currently, there's no way to specify where the dependecies are coming from. Given the current dependencies resolution mechanism, dependencies can be injected in the resolution tree by creating a CatalogSource with higher priority containing an operator with the same name. That's unsafe for Managed Services.

The only way around is to add the bundles of all the dependencies into the same catalog as the main operator, but that creates duplication and overhead for the Managed Services teams. Also, considering the dependencies might also have their dependencies, using this workaround pretty much means duplicating the content of all the catalogs in each operator's catalog.

Acceptance criteria:

• OLM dependencies should allow the specification of the CatalogSource to use for each dependency.