Dependency Library + CLI - next steps

[m1kola]

Since #206 we have PoC CLI which is:

• Capable of resolving off-cluster (doesn't require a cluster at all)
• Takes package name, channel (optional) and version (optional) as input for resulution
• It also take either a local directory with FBC or an image ref with FBC catalog (just one for now)
• Optionally it also takes a directory with yaml manifests. If manifests contain Operator objects, they will be used as input into the solver (list of required packages - similar to Operator objects installed in the cluster when running on-cluster resoltion).

Next steps:

• Gather feedback from the community using this GitHub discussion - https://github.com/operator-framework/operator-controller/discussions/262
• Plan next iterations based on feedback

Also there are a few things going in parallel. For example, we will likely change significantly how we build resolution problems (see operator-framework/deppy#96 and relevant RFC). Once we have more or less stable way to build the resolution problem - we will be able to create some sort of library to share between operator-controller and resolution CLI.

This is still valid.

Originally posted by @m1kola in https://github.com/operator-framework/operator-controller/issues/206#issuecomment-1641720499

[m1kola]

We removed Deppy solver and CLI tool from the codebase. So closing this for now.