As a user, I want to be able to browse OLM v1 operators in a UI comparable to OperatorHub. Currently, rendering such a catalog UI requires fetching all bundles and packages from the catalogd service, and doing complex business logic to transform FBC into the CatalogItem API. This all has to happen on the frontend, which makes performance sluggish. This story will move that process into our backend, which will allow us to fetch CatalogItem JSON data directly, enabling a snappy catalog UI experience.

AC:

• A suitable, internal backend API is designed which provides CatalogItem data in JSON form
• a new process will be added to the console backend to consume FBC from the catalogd service and transform it into CatalogItems, which will be stored on disk or possibly in memory if not too cumbersome.
• A new endpoint is added to the console service, which will serve the new CatalogItem JSON data
• Business logic for transforming FBC into CatlogItems will be unit tested

Stretch:

• A controller will be implemented which watches ClusterCatalogs and re-syncs catalog data when updates occur