Story

Include catalog metadata content consistency check during export workflow

As part of the export-dynamic.yaml GH reusable workflow, after the export-dynamic step, we should check, for every  metadata/ yaml file of the overlay workspace folder, that:

• a plugin exists in plugins as part of the plugins (in the source folder) references in the `plugins-list.yaml` file of the overlay, with the same name in the plugin package.json, as the packageName field of the metadata yaml file,
• the version field in the metadata yaml file is the same as the version in the corresponding plugin package.json
• if the dynamicArtifact field of the metadata yaml file is set to be an oci reference (start by oci://ghcr.io) :
  • its tag should be of the form: <image-tag-prefix input><plugin version>
  • its reference (without the tag), should be of the form: <image-repository-prefix input>/<package name with @ and / replaced by - >
• the backstage.supportedVersions field in the metadata yaml file is at the same major and minor version (ignore patch level) as the supportedVersions field in the dist-dynamic/package.json of the corresponding source plugin

We should fail if those checks are not met.

We should report a detailed list of metadata mismatches in the GH workflow summary, and as an additional output of the workflow that can be retrieved by calling workflows.