[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.

La issue propone di aggiungere metadati dichiarativi agli schemi di catalogo. Inizia leggendo le definizioni esistenti degli schemi di catalogo e le issue correlate #2197 e #1528. Comprendi i concetti di ruoli semantici, origini dei nomi accessibili, slot strutturali e binding dello stato. Determina dove vengono attualmente elaborati i metadati del catalogo nella codebase e come estenderli senza callback eseguibili.

Scritto dal modello di indicizzazione a partire dal testo della issue.