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/collections/scenarios/Bulk Remove Books - Single Book.yml

@@ -8,20 +8,10 @@ http:
   auth: inherit
   body:
     type: json
-    jsonBody: "{\n    \"book_ids\": [\n      \"{{bookId1"
+    data: "{\n    \"book_ids\": [\n      \"{{bookId1"
   headers:
   - key: Content-Type
     value: application/json
   - key: Authorization
     value: Bearer {{authToken
-
-docs: |-
-  ## Bulk Remove Books - Single Book
-  
-    Tests that bulk remove endpoint works correctly with a single book.
-  
-    **Expected Result:** 200 OK with removed: 1, total: 1
-  
-    **Purpose:** Verifies the bulk remove endpoint handles single-item arrays correctly, providing flexibility for clients to use the same endpoint for both single and multiple removals.
-  
-    **Note:** Using bulk remove for a single book is functionally equivalent to the single remove endpoint but allows for consistent error handling and response format.
+docs: "## Bulk Remove Books - Single Book\n\n  Tests that bulk remove endpoint works correctly with a single book.\n\n  **Expected Result:** 200 OK with removed: 1, total: 1\n\n  **Purpose:** Verifies the bulk remove endpoint handles single-item arrays correctly, providing flexibility for clients to use the same endpoint for both single and multiple removals.\n\n  **Note:** Using bulk remove for a single book is functionally equivalent to the single remove endpoint but allows for consistent error handling and response format."