Feature Overview (aka. Goal Summary)

Customers want to customize the catalog entity tabs and cards, but they can't because the tabs "Overview", "Dependencies" and "API" are hardcoded and not loaded from a dynamic plugins. All tabs and cards should be loaded and configured the same way.

This is a follow-up on RHDHBUGS-161 (customer can't configure the entities as needed) and related to RHIDP-5207 (similar feature for the user-settings page).

Goals (aka. expected user outcomes)

1. Also core tabs and cards should be exported and loaded via the dynamic plugin feature.
2. Layout and positioning of these cards should be done in the "dynamic-plugins.default.yaml" instead of code.
3. TBD: Layout options are currently passed to the MUI Grid option. Maybe this could be improved? Currently it's not possible to define a specific layout for cards... Maybe it's a non goal anyway?
4. The layout options for the catalog entity tabs and cards should be documented or updated. (See also RHIDP-5604)

Requirements (aka. Acceptance Criteria):

1. Overview, Dependencies and API tab layouts are defined in a YAML.
2. All these tabs can be reordered and customized.
3. TBD: Is a new plugin required to export these cards from @backstage/catalog?

Out of Scope (Optional)

TBD:
New frontend system and complex layout features are not part of this feature. The focus is to replace the hard coded tabs with features we have already.

Customer Considerations (Optional)

Documentation Considerations

Documentation on the new defaults and customization options needs to be created or updated.