chore(backstage): Add catalog-info.yaml config file

[jburns24]

This pull request adds a Backstage entity metadata file to this repository so that the component can be added to the Liatrio's Backstage software catalog.

After this pull request is merged, the component will become available.

For more information, read an overview of the Backstage software catalog.

[caseyw]

@jburns24 I'd probably add some tags, so we can see them listed in the catalog view. It'd allow us to do some sorting, searching, etc.

[jburns24]

@caseyw I was considering tags but was unsure what good tags for this component should be. Poor tagging in a system like Backstage would hurt sorting and searching. While a good tagging convention helps. These workflows are used for a wide variety of things and the repo name is the best generalized tag I could think of. Now maybe github-wrokflows is the tag we should put here?

Given the risk of adding crap tags I was thinking I would hold off on that until we came up with some tagging standards or something of the sort. Mostly I want to get this in so I can start building out relationships with other repos.

If you think missing tagging blocks the PR I would appreciate input on what kind of tags you think would be valuable for a repo like this.

[caseyw]

You're absolutely right. The way @gesparza3 explained it to me is that tags represent the repository. So in this case I think it would be GitHub and workflows, and any tech used to make that happen.

Examples:
https://github.com/liatrio/gratibot/blob/main/catalog-info.yaml
https://github.com/liatrio/openo11y.dev/blob/main/catalog-info.yaml

I'd defer to @gesparza3 in the end.