Task

As an engineer working on RHDH, I want to demonstrate the typescript only connector against upstream kubeflow

Background

• The folks on the RHOAI model registry (old name) / ai hub (new name) team (#forum-openshift-ai-model-registry and #openshift-ai-hub-devs) have curated both a dev env for standing up model reg/catalog on kind over at https://github.com/kubeflow/model-registry/tree/main/devenv 
• they also have install methods linked from the main readme
• and they have a doc link to using their upstream version of the UI in the README as well
•  

Dependencies and Blockers

No QE or Doc dependencies 

Acceptance Criteria

Using the output from RHIDP-11757, stand up upstream versions of the registry, catalog, and if possible UI, and demonstrate population of the registry that leads the importing of that content into the backstage catalog as Resources when the typescript only form of the connector is integrated with the upstream registry/catalog.

Make updates as needed to the connector to work with upstream vs. RHOAI/ODH

STRETCH:  If possible, confirm/deny whether any of what import from the catalog to the registry is possible upstream like with mid/down stream that would facilitate retrieval of model cards for tech docs.