fix(bruno): convert drifted body keys to body.data — CLI scenario runs now carry bodies

Follow-up to the sweep route audit, correcting its diagnosis: the CLI
DOES read .yml bodies — via OpenCollection's `body.data` string form
(the NewDevDBSetup script always worked because it used it). The
failing scenario POSTs used `body.json` (structured) / `body.jsonBody`
(string) — keys the CLI silently ignores, sending Content-Length: 0
with form-urlencoded content-type, so every server bind failed.

- 81 bodies converted to data-form (json maps serialized; jsonBody
  strings kept verbatim, {{vars}} intact).
- 6 pre-existing TRUNCATED payloads repaired: the original generator
  cut bodies at the first {{var}} (every SHA-256-identified scenario
  plus Sync Progress/Sync Bookmarks shipped mid-JSON and 400'd from
  day one). Rewritten whole, faithful to each file's documented
  purpose; book_sha256/book_uuid added to the environment.
- environments: opds_base_url correction from the sweep retained.

Verified live against the rebuilt dev container: the full koreader
scenario tree runs green through `bru run` — 14/14 (202s across
immediate/checkpoint/SHA-256 progress, 200s bookmarks, highlights,
notes; SHA-256 book identification exercised against a real
file_sha256).

bruno/dashboard/restore-system-collection.yml

@@ -8,40 +8,9 @@ http:
   auth: inherit
   body:
     type: json
-    jsonBody: "{\n  \"collection_name\": \"continue-reading\"\n}"
+    data: "{\n  \"collection_name\": \"continue-reading\"\n}"
 runtime:
   scripts:
   - type: tests
-    code: "test(\"status must be 200 with valid collection\", function() {\n    expect(res.status).to.eql(200);\n\
-      });\n\ntest(\"response has success message\", function() {\n    expect(res.body.message).to.exist;\n\
-      });"
-
-docs: |-
-  Restore a system collection to its default state.
-
-  **Endpoint**: POST /api/dashboard/restore-system-collection
-  **Auth**: Required (Bearer token)
-
-  ## Request Body
-
-  | Field | Type | Required | Description |
-  |-------|------|----------|-------------|
-  | collection_name | string | Yes | Name of system collection to restore |
-
-  Valid collection names:
-  - `continue-reading`: Books you're currently reading (0 < progress < 1)
-  - `recently-added`: Newly added items to this library
-  - `recently-read`: Books you've finished (progress >= 1)
-  - `not-started`: Books you haven't read yet (progress = 0 or no record)
-
-  ## Example Request
-
-  ```json
-  {
-    "collection_name": "continue-reading"
-  }
-  ```
-
-  ## Response
-
-  Returns success message on restore.
+    code: "test(\"status must be 200 with valid collection\", function() {\n    expect(res.status).to.eql(200);\n});\n\ntest(\"response has success message\", function() {\n    expect(res.body.message).to.exist;\n});"
+docs: "Restore a system collection to its default state.\n\n**Endpoint**: POST /api/dashboard/restore-system-collection\n**Auth**: Required (Bearer token)\n\n## Request Body\n\n| Field | Type | Required | Description |\n|-------|------|----------|-------------|\n| collection_name | string | Yes | Name of system collection to restore |\n\nValid collection names:\n- `continue-reading`: Books you're currently reading (0 < progress < 1)\n- `recently-added`: Newly added items to this library\n- `recently-read`: Books you've finished (progress >= 1)\n- `not-started`: Books you haven't read yet (progress = 0 or no record)\n\n## Example Request\n\n```json\n{\n  \"collection_name\": \"continue-reading\"\n}\n```\n\n## Response\n\nReturns success message on restore."