[FEATURE]: Add catalog semantics metadata for roles, names, state, and interactions

- [x] I have searched the existing issues to make sure this feature has not already been requested.

## Is your feature request related to a problem? Please describe.

Catalog schemas describe wire shape but not framework-neutral semantic role, accessible-name source, structural child slots, state/value bindings, or supported interactions. Renderers know this behavior in code; accessibility, testing, inspection, and policy tools otherwise hard-code component names or infer arbitrary property names.

## Describe the Proposed Solution

Define optional versioned declarative catalog metadata for semantic role, accessible-name source/normalization, structural slots, value/data-path and enabled/selected/checked/validation sources, and supported interactions with their binding/action property. Include it in catalog version/digest inputs. It must contain no executable callbacks, and tooling should fail closed when required metadata is absent.

## Describe Alternatives Considered

Component-name inference fails for custom catalogs. Inspecting Flutter widgets or a DOM is renderer-specific. Private registries fragment semantics and drift from the advertised catalog.

## Additional Context

#2197 covers action intent and #1528 covers schema-driven child resolution; both are complementary to this broader catalog-owned semantics contract.

L’issue propose d’ajouter des métadonnées déclaratives aux schémas de catalogue. Commencez par lire les définitions existantes des schémas de catalogue ainsi que les issues associées #2197 et #1528. Comprenez les concepts de rôles sémantiques, de sources de nom accessible, de slots structurels et de liaisons d’état. Déterminez où les métadonnées de catalogue sont actuellement traitées dans la base de code et comment les étendre sans callbacks exécutables.

Rédigé par le modèle d'indexation à partir du texte de l'issue.