refactor: model product dependencies and simplify qualification - #209

Product builds previously depended on shared release machinery, bundled optional resources, and inconsistent task boundaries. This change gives runtimes, SDKs, database resources, PostgreSQL tools, extensions, and the PG-wire server explicit ownership and dependency edges.

• SDKs expose ecosystem-native build, test and package commands through Moon. Transitive source changes invalidate dependent checks; jobs consuming transferred artifacts execute against those bytes without rebuilding producers or reusing incomplete consumer hashes.
• Seeds and ICU data are separately selectable resources. WASIX core compilation is separated from optional tools and extensions. Native bindings are shared across Rust, Node and mobile adapters; the desktop broker uses PostgreSQL wire messages for database operations.
• Release Please generates and validates one local candidate before the PR is pushed. Publication consumes qualified outputs, freezes packages, bootstraps only missing names, reconciles immutable public bytes and promotes last. Candidate assembly no longer installs product compilers; GitHub request coordination retains bounded state.
• Maintainer orchestration uses Shell and Bun TypeScript. Tests and fixtures live with their owners; redundant layout/source assertions and obsolete wrappers are removed. Docs describe current ownership and distinguish source qualification from publication controls.

Validation includes the complete release aggregate, workflow/affectedness and artifact-transfer checks, all 58 formatting/lint tasks, archive corruption and recovery scenarios, and native/WASIX consumer tests. Installed Node, Bun, Deno and Rust consumers pass with independently differing SDK/runtime/extension/resource versions; SQL, pgTAP and ICU behavior pass, and repeated candidate preparation produces identical Git trees.

This does not complete platform qualification. Deno retains its FFI path; final native target, Windows/MSVC, Apple/SwiftPM and mobile-device qualification remains pending. No release or registry publication is performed by this PR.