fix(ui-wasm): #1392 wire reactive state + setText on web/wasm target

[proggeramlug]

Fixes #1392.

Problem

On the web/wasm target (what the playground hub compiles to), perry/ui's reactive state and imperative setText were silent no-ops:

• count.text() showed the initial value and never changed after set.
• count.value read undefined.
• setText(id, value) dispatched to nothing; Text(content, id)'s 2nd id arg was dropped.

Root cause

The state_desugar HIR pass (crates/perry-transform/src/state_desugar.rs) lowers state<T> to a synthetic, string-keyed registry API: __state_init / __state_get / __state_set, the 2-arg Text(content, id) form, plus __foreach_register and __navstack_register_route. The native LLVM backend special-cases these (lower_call/native/mod.rs) and backs them with perry-runtime/src/ui_text_registry.rs. But neither the wasm backend (perry-codegen-wasm) nor the JS backend (perry-codegen-js) implemented them:

• __state_* resolved to perry_ui_unknown / __perry.perry_ui___state_* (nonexistent).
• perry_ui_text_create ignored its 2nd id arg.
• there was no perry_ui_set_text.

Fix

Mirrors the native model — the synth id is reused as both the state key and the Text widget's setText id, so a write fans out to every bound widget.

Emit — map the synthetic methods to keyed bridge functions:

• crates/perry-codegen-wasm/src/emit/ui_method_map.rs
• crates/perry-codegen-js/src/emit/calls.rs

Runtime (wasm_runtime.js + web_runtime.js):

• keyed-state registry (perry_ui_state_init / perry_ui_state_get_keyed / perry_ui_state_set_keyed)
• perry_ui_set_text(id, value) + an id→widget text registry
• perry_ui_text_create(text, id) registers the 2-arg form
• perry_ui_foreach_register / perry_ui_navstack_register_route keyed dispatch
• all registered in __perryUiDispatch (wasm) / window.__perry (js)

Verification

• Compiled the issue's counter repro to --target wasm; bridge names now resolve (perry_ui_state_init / _get_keyed / _set_keyed, 2-arg perry_ui_text_create) — no more perry_ui_unknown.
• End-to-end: booted the compiled counter wasm in Node with a DOM mock — button click fires, bound Text re-renders 0 → 1 → 2, and count.value reads correctly (console.log prints val 1, val 2, not val undefined).
• Behavioral unit tests over the real wasm_runtime.js and web_runtime.js pass for keyed get/set, reactive Text, 2-arg Text, and imperative setText.
• cargo fmt --all -- --check clean; perry-codegen-wasm / perry-codegen-js / perry-dispatch / perry-transform tests pass.

Note: version bump + CHANGELOG entry intentionally omitted (folded in at merge per repo workflow).