Test: carry uwreqs.challenge_id in the swap-scenario fixture

[heifner]

master does not compile. Every E2E run since the underwriter-challenge merges dies in the platform build, before a single flow starts:

packages/cluster-tool prepare: tests/flow/contexts/SwapScenarioContext.test.ts(58,3): error TS2322:
  Property 'challenge_id' is optional in type '{ ... }' but required in type 'SysioUwritUwRequestTType'

Cause

wire-sysio#549 adds challenge_id to both uw_request_t and the locks row — the marker holdlocks stamps while an underwriter-fault challenge is open. wire-libraries-ts#61 regenerated SysioContractTypes, so the field is a required property on SysioUwritUwRequestTType and SysioUwritLockEntryType.

#56 carried the new field into lockRow() but not into uwreqRow(). Both fixtures return the full row type rather than a Partial, so the omission fails tsc -b in packages/cluster-tool and takes pnpm build — and the E2E gate behind it — down with it.

Same break as #58, which added target_amount to this same fixture for the same reason.

Fix

     attestation_outbound_data: "",
+    challenge_id: 0,
     ...overrides

Scope

uwreqRow() and lockRow() are the only positions in the repo that construct these rows; every other SysioUwritUwRequestTType reference is a read position. Key-diffing every generated-type literal in the tree against the wire-libraries-ts master interfaces leaves nothing else short a required field: reserveRow 22/22, uwreqRow 23/23 with this line, lockRow 10/10, and the three SysioSystem*/SysioBios* literals in the orchestration tests complete.