feat(web_core): add WebComponentImplementation helpers and refactor basic catalog

[josemontespg]

Overview

Implements the createWebComponentImplementation helper function and isWebComponentImplementation type guard in @a2ui/web_core/v0_9, and refactors all basic Lit components in renderers/web_core/src/v0_9/basic_catalog/components/ to export definitions using createWebComponentImplementation.

Key Changes

• @a2ui/web_core/v0_9:
  • createWebComponentImplementation: Pairs a ComponentApi definition, Custom Element class, and tag name into a WebComponentImplementation, automatically registering the element in customElements if not already defined.
  • isWebComponentImplementation: Structural duck-typing check verifying whether a component definition specifies a valid string tagName.
• Basic Catalog components:
  • Refactored all 18 basic catalog components (AudioPlayer, Button, Card, CheckBox, ChoicePicker, Column, DateTimeInput, Divider, Icon, Image, List, Modal, Row, Slider, Tabs, Text, TextField, Video) to export universal definitions using createWebComponentImplementation.
• Unit Tests: Added test suites for createWebComponentImplementation and isWebComponentImplementation.

Verification

• yarn --cwd renderers/web_core test (all 474 unit and conformance tests pass)
• yarn --cwd renderers/web_core lint (clean, 0 errors)
• ./scripts/fix_format.sh --check (passes)

[gemini-code-assist]

Code Review

This pull request introduces the isWebComponentImplementation type guard function to check if a component API or implementation is a WebComponentImplementation, along with corresponding unit tests and a changelog entry. The feedback suggests improving the type guard by also validating the presence and types of name and schema properties, as WebComponentImplementation extends ComponentApi and requires these fields for full type safety.

[ditman]

(Same comment as in the previous entry, maybe it's enough to export createWebComponentImplementation and isWebComponentImplementation to users of web_core (the catalog implementers) and they can create this glue over there?

Or maybe all catalogs are going to use these A2uiAudioPlayer implementation instead of the Element? In that case, do we need to re-export the A2uiAudioPlayerElement custom element implementation?

My hunch is that we don't need to export both the WebComponentImplementation and the BasicCatalogA2uiLitElement classes?