chore: add catalog info for backstage

[brian-smith-tcril]

No description provided.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (d749793) 99.47% compared to head (dc14a93) 99.47%.

❗ Current head dc14a93 differs from pull request most recent head 1f1d850. Consider uploading reports for the commit 1f1d850 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #130   +/-   ##
=======================================
  Coverage   99.47%   99.47%           
=======================================
  Files          10       10           
  Lines         381      381           
  Branches       28       28           
=======================================
  Hits          379      379           
  Partials        2        2           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[feanil]

Couple of things you can get rid of but then I think this is good to land. I don't need another review if you are dropping those too things I pointed out.

[feanil]

You don't need this, see the example here for the latest best practice for catalog-info.yaml: https://docs.openedx.org/projects/openedx-proposals/en/latest/processes/oep-0055/decisions/0001-use-backstage-to-support-maintainers.html#references

[feanil]

This gets auto linked so you don't need to do it explicitly.

[brian-smith-tcril]

@feanil just to confirm before I update this

apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
  name: 'i18n-tools'
  description: "Tools to help with internationalization and localization of Open edX projects"
spec:
  owner: domain-translations
  type: 'library'
  lifecycle: 'production'

is all we need?

[feanil]

Yep, that looks right to me.