[jeremi]

Moves the Casework, BReg and Evidence adaptors to @registrystack/client 0.45.0. Main still calls routes and methods the current server no longer serves, and expects snake_case validation codes where the server now sends kebab-case.

Changes

• Casework: the work-item operations are replaced by the review task routes (listCaseworkReviewTasks, getCaseworkReviewTask). The task-grant operations move to the current routes, and the producer review path sends the registry-review-profile header.
• BReg: createChangeRequest, executeLifecycleAction and jobs/create-and-submit.js are removed. The 0.45.0 client has Actions and Proposals in their place, and this PR does not wrap them. getEntitySchema becomes getRecordSchema. Refusals carry refusalCode and reasonCode.
• Evidence: moves to the progressive request handle, the EvidenceClientProfile envelope, and mapping output forms.
• Validation and error codes are kebab-case throughout.
• Config is renamed to attemptTimeoutMilliseconds and maximumResponseBytes; the maxResponseBytes alias is gone.
• Removed: the @openfn/language-registry-relay package (the 0.45.0 client has no Relay namespace) and the pilot correction workflow, which called the removed BReg operations.

Checks run locally

• Unit suites: evidence 18/18, breg 13/13, casework 18/18, events 34/34.
• Pilot: JS 27/27, Python 28/28.
• npm test passes; pack:dry-run runs without error.

Not done yet

• The container pilot (deployment/, pilot/agriculture/) still pins the 0.38 server, so the CI pilot job will fail until it is repinned to 0.45.0.
• pilot/smoke.py, prepare.py and agriculture/registry.yaml still use the 0.38 correction and submit_request flow.
• The event bridge request_lifecycle trigger is unchanged; it is not yet confirmed that 0.45.0 still emits it.
• No Actions or Proposals operations for BReg yet.