Package-level marketplace catalog entities would be generated in the overlay repository:

• partly from low-level in the backend or frontend plugin `package.json`,
• partly with the sha-based OCI reference of the published plugin OCI artifact,
• partly from minimal user-provided source metadata (like package name, default or additional example plugin configuration, support, lifecycle, etc ...).

So in the overlay we should provide (in each related workspace) the minimal required, user-provided metadata to allow generating the package-level marketplace catalog entities when building the catalog container image.
This issue is about defining the structure, in the overlay, of this package-related metadata that will seed generation of package-level catalog entities.