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

El issue propone añadir metadatos declarativos a los esquemas de catálogo. Empieza leyendo las definiciones existentes de los esquemas de catálogo y los issues relacionados #2197 y #1528. Comprende los conceptos de roles semánticos, fuentes de nombres accesibles, slots estructurales y enlaces de estado. Determina dónde se procesan actualmente los metadatos del catálogo en la base de código y cómo ampliarlos sin callbacks ejecutables.

Escrito por el modelo de indexación a partir del texto del issue.