Task Description (Required)

Based on the AI catalog structure that will be defined in DEVAI-10 (specifically DEVAI-147, DEVAI-148, and DEVAI-149), implement an AI asset catalog in backstage based on one or more real examples.

Some options to consider (one or both):

• Use the model-service stood up for our team as a basis, as it provides: A deployed model and model server, an API gateway, instructions for access, and usage restrictions. Link: https://model-service.apps.rosa.redhat-ai-dev.m6no.p3.openshiftapps.com/
• Ollama deployed on OpenShift with multiple models, perhaps utilizing https://github.com/williamcaban/ollama-ubi as the image & deployment manifests

At a minimum, the AI catalog should have the following, regardless of the scenario used:

• Model Server represented as a Component
• Model(s) represented as Resources
• Model server APIs represented as APIs
• Finally, instructions for the model, model server, and anything else, modelled as techdocs, based on DEVAI-148 and DEVAI-149

https://github.com/redhat-ai-dev/model-catalog should be used as the repository to store the AI catalog resources .