feat(liquid): activate manifest transactions and release 1.1.0-rc.0

[lukachi]

Summary

Final PR in the confidential-transaction manifest merge train. This branch is stacked on #17 and activates the complete reviewed flow:

• parses and reviews a manifest before any signing material is acquired
• renders clear signing intent, including whether the transaction will be broadcast
• resolves account-scoped wallet inputs and short-lived signing material
• assembles and finalizes a concrete smplx-wasm transaction with covenant inputs, deterministic input order, signatures/witnesses, issuance bindings, outputs, blinding, and raw-byte guards
• optionally broadcasts the finished transaction and returns the network txid
• exposes Liquid contract identity and Receive views for confidential and unconfidential addresses
• funds unconfidential recipients through the explicit-output builder path
• activates the real p2pk Pay/Receive web example and publishes the AppKit result type

Release and CI

• sets the workspace and extension release to 1.1.0-rc.0
• emits Chrome-compatible manifest version: 1.1.0.0 with version_name: 1.1.0-rc.0
• records the expected smplx compiler version and checks the built WASM package before production builds
• restores the complete root gate: extension, packages, web, lint, format, and tests
• aligns React/CSS/Zod dependency types so a clean frozen install passes that gate

Validation

Validated from an isolated checkout at c08c6c6b91655f4b7cb7c2f9f3c429c3fffd849d with the committed LWK and smplx submodule revisions:

• rebuilt smplx/crates/wasm/pkg at 8f0215ce1d63ab9dc5c1310151a12840240f1026
• rebuilt lwk/lwk_wasm/pkg at 693c4fb328eceb7bc858a0ee7a63752bce6b1a94
• bun install --frozen-lockfile
• bun run check — 836 tests pass, 0 fail
• bun run build
• bun run web:build
• generated extension manifest inspected: 1.1.0.0 / 1.1.0-rc.0

Stack

• Base: feat(extension): add clear-signing manifest review #17 (feature/tx-manifest-clear-signing)
• Head: feature/tx-manifest-activation

Known release follow-up

Chrome compares the numeric manifest version, so the required RC encoding 1.1.0.0 will not be superseded by a later stable 1.1.0. That promotion behavior is tracked as follow-up release debt and is intentionally not widened into this final activation PR.