cli: extend managed deadlines and prepare bounded transports

[aaltshuler]

Managed queries and mutations can exceed the current 10-second request
deadline while the server is still working. Increase their total deadline to
30 seconds, including connection establishment and response reading, while
retaining the 10-second connection limit. Redirects and automatic retries are
disabled, responses remain bounded to 8 MiB, and a timed-out mutation may have
committed and requires independent reconciliation.

Also prepare bounded transport for the existing NDJSON load and native commit
list/show endpoints. Load checks the exact UTF-8 input against a 32 MiB limit
before dispatch and has its own 300-second request deadline. Prepared commit
reads share the 30-second managed request deadline. Server fixtures preserve
signed graph/action ceilings, Cedar authorization, branch-creation checks and
authenticated commit attribution.

The command activation boundary follows
RFC 0059 / PR #675:

• CC-11 now specifies the same 10-second connect and 30-second total
  query/mutation limits. This narrow agreement does not accept the broader RFC.
• CC-06 / CC-14 keep load, commit list and commit show on ordinary
  addressing; these commands do not acquire credentials from folder context.
• Activation remains subject to CC-05 / CC-07 / CC-10 / CC-17: common
  connection selection, exact API/cluster/endpoint binding, action mapping and
  destination/effect evidence. The prepared transport alone does not qualify
  those commands. Accepted served-catalog scope in CLI: support queries list through --server and --graph #653 remains separate.

RFC 0053 records the implemented limits and preparation boundary. User docs
and release notes describe the query/mutation deadline change.

Local validation passed: all 110 CLI unit tests, strict all-target workspace
Clippy in both the default and failpoint feature configurations, formatting,
documentation checks (133 Markdown files), spelling and diff checks. The
deadline regressions fail with the old 10-second limit and pass with 30 seconds;
they preserve complete successful receipts after 10 seconds and observe one
request on timeout across ad-hoc, stored, conditional and branch mutations.