Update all repos to move release data to catalog-info.yaml

[feanil]

In some cases, the file will already exist and need to be updated, and in others, it won't exist and will need to be created. Other fields can be left blank for now in the case of creation.

Don't remove the old openedx.yaml file in this step, we will do that as future work in a different ticket.

[kdmccormick]

@irtazaakram When you switch a repo over to catalog-info, make sure that you set the release branch value to whatever it was in openedx.yaml, usually "master" or "main". Setting it to null removes it from the release.

[salman2013]

@feanil is there need to add release data like openedx.org/release: "master" in catalog.yaml file, when openedx.yaml don't have release tag. One particular example is https://github.com/openedx/edx-ora2/blob/master/openedx.yaml

[kdmccormick]

@salman2013 If there is no release data in openedx.yaml, then that means that the repository shouldn't be tagged (most likely because it is a package, which is installed into a tagged repository). The catalog-info file should either have openedx.org/release: null, or simply not have the openedx.org/release key at all--either is OK.