fix(codex): support goal pause and resume

[berialcheng]

Summary

Happy currently treats /goal resume as a new goal objective and does not expose Codex's paused state in the shared Web/mobile UI. This follow-up to #1428 wires Codex's provider-owned pause/resume lifecycle through the app-server, CLI session state, and Happy's shared Expo client.

What changed

• send status-only thread/goal/set requests for pause/resume without replacing the objective
• preserve active, paused, blocked, and limited states in a backward-compatible V2 agent-state projection while keeping V1 intact
• add state-aware Pause/Resume controls to Web, iOS, and Android, including RPC error feedback
• isolate /goal control commands from prompt batching and prevent failed controls from becoming model turns
• reconcile thread resets, reconnects, session swaps, concurrent mutations, and stale provider notifications

Compatibility

Older apps continue reading the unchanged V1 goal projection and ignore V2. Newer apps prefer V2 and safely fall back to V1 when the CLI is older or V2 is stale or malformed.

Verification

• git diff --check HEAD^ HEAD
• added focused test coverage for protocol payloads, command isolation, state projections, session swaps, UI actions, and RPC errors
• per request, local build, typecheck, and test suites were not run