As a Plugin Developer, I want to use a dynamic plugin extension point to contribute a custom alert banner to a catalog, so that I can inform users about important context, system status, or required actions related to the catalog's content.

🚀 Acceptance Criteria

• A new extension point type is defined in the dynamic plugin SDK (e.g., console.catalog/alert).

• The new extension's properties must allow a plugin to specify:

• • A catalogId to target a specific catalog (e.g., 'OperatorHub', 'DeveloperCatalog').

• • An optional type (or itemType) property to target a specific catalog item type (e.g., 'BuilderImage', 'Devfile').

• • The React component to be rendered (e.g., a PatternFly Alert component).

• • An optional priority property for sorting multiple contributed alerts.

• The console's shared Catalog component (or the internal logic that renders catalogs) is updated to consume extensions of this new type.

• Contributed alert components are rendered in a designated area at the top of the catalog page (e.g., above the toolbar or items).

• Documentation for the new extension point and its properties is added to the plugin SDK documentation.

• The implementation of this extension point does not cause any visible UI changes to existing catalogs by default (i..e., until a plugin actively uses it).