[runtime] Make schema chain test deterministic

[GsCommand]

Motivation

• The end-to-end signing chain test was flaky on CI because the spawned server sometimes booted with schema verify doing a full fetch/compile, causing the client to abort during /verify?schema=1 on cold start instead of following the cached-only warmup path.

Description

• In runtime/tests/runtime-signing.test.mjs updated the startServer({ ... }) env block for the failing chain test to set VERIFY_SCHEMA_CACHED_ONLY: "1", VERIFY_MAX_MS: "12000", SCHEMA_FETCH_TIMEOUT_MS: "3000", and SCHEMA_VALIDATE_BUDGET_MS: "3000" and removed the previous explicit VERIFY_SCHEMA_CACHED_ONLY: "0" setting.
• Kept the existing chain-step logging lines ([chain] before clean request, [chain] after clean response, [chain] before summarize request, [chain] after summarize response, [chain] before classify request, [chain] after classify response, [chain] before verify request) intact.
• Extended the test's verify flow to handle the cached-only warmup deterministically by calling /verify?schema=1 and, if the response is 202, logging the warmup, waiting 1200ms, retrying once, and if the retry still does not return 200 throwing an error with full status and body text; otherwise continue with unchanged assertions including schema_valid === true.
• Scope of change is limited to the single test file runtime/tests/runtime-signing.test.mjs and does not modify any runtime logic or other tests.

Testing

• Ran the unit tests for the file with npm test -- --runInBand runtime/tests/runtime-signing.test.mjs and the test file passed locally (all subtests in runtime/tests/runtime-signing.test.mjs succeeded).
• Ran git diff --check to validate there are no diff-check issues.

Exact changes: set cached-only verification environment variables in the failing chain test and add a single 202->retry handling path for /verify?schema=1 while preserving assertions and logging.

---

Codex Task