feat(runtime): freeze application time and input across host pauses

[replghost]

Summary

• Add canonical application pause/resume boundaries for browser and native execution: stop guest updates, freeze monotonic time, discard queued gameplay/audio, and retain releases and host state.
• Add optional bounded capabilities.deviceInput.controls help metadata without introducing a new input-mapping ABI.
• Regenerate matching browser Wasm, worker, and embedded artifacts.

Stack and scope

Based on #57 (feat/mediated-input, e60a613), the exact runtime revision already consumed by Dotli #185. This keeps the PR diff limited to pause/control-help support rather than duplicating its runtime prerequisites. No new scheduler tuning, Chat authority, wallet integration, or deployment.

Consumers: paritytech/dotli-community#185 and paritytech/polkavm-app-kit#68. Worker and Wasm must be updated together because pause adds a Wasm input-queue boundary export.

Verification

• All 156 workspace tests with all features passed, including embedded asset digest verification. Workspace Clippy with all targets/features and warnings denied passed after restricting the Wasm-only bridge to its target.
• 36 browser-worker tests passed, including both execution backends, startup pause, exact exclusion of suspended time, queued-tick suppression, and stop-during-startup.
• Regenerated artifact checksums match a fresh source build.
• Local Chromium exercised pause/resume against the real emulator: frame and audio output stopped while paused and resumed.

No PR merge or deployment is requested by this change.