Task Description (Required)

The team is pivoting from using the classic catalog-info.yaml as the data format for providing AI Model Catalog information to a JSON schema which will then be translated by code running in backstage to Components, Resources, APIs, etc.

The normalizer logic of the bridge located at https://github.com/redhat-ai-dev/model-catalog-bridge/tree/main/pkg/cmd/cli will have to be reworked to produce the new JSON schema

The unit testing logic at https://github.com/redhat-ai-dev/model-catalog-bridge/tree/main/test/stub  where catalog-info.yaml styled results were checked will have to be reworked

Lastly, for the current set of normalizers, use of https://pkg.go.dev/github.com/elastic/go-json-schema-generate to generate golang structs and validation code will be needed.

Chief benefits of this new "unit of exchange"

• centralize actual use of the backstage types in backstage based typescript libraries where that type is up to date
• decouple dependency of backstage type generation into other languages like golang

Dependencies for coding:  https://issues.redhat.com/browse/RHDHPAI-608 

Dependencies for testing against backstage:  https://issues.redhat.com/browse/RHDHPAI-609 

Posslble package rename from cli to client where appropriate