fix: prettier format failure in `subscriptionReplay.test.js`

[heskew]

Context

The `Format Check` CI job is currently failing on `main` with prettier flagging `unitTests/resources/subscriptionReplay.test.js`. Reported by the CI run on #547:

```
[warn] unitTests/resources/subscriptionReplay.test.js
[warn] Code style issues found in the above file. Run Prettier with --write to fix.
##[error]Process completed with exit code 1.
```

Run: https://github.com/HarperFast/harper/actions/runs/25920310025/job/76187304210

The file was recently modified by commit `8bbbc4c2` "yield every 100 entries in subscription catchup" which presumably introduced the formatting drift.

Goal

Run prettier with `--write` on `unitTests/resources/subscriptionReplay.test.js` and commit the result.

Approach

```
npm run format:check # confirm the failure surfaces locally
npm run format:write -- unitTests/resources/subscriptionReplay.test.js
npm run format:check # confirm clean
```

If the diff has unrelated drift in other files, scope the commit to just this file and flag the rest as a follow-up.

Success criteria

• `npm run format:check` passes
• The `Format Check` CI job passes on the resulting PR
• No functional changes to the test file (only whitespace/formatting)

Scope

• Single-file formatting fix only
• Do NOT modify test logic or assertions
• Do NOT re-format unrelated files in the same PR

[claude]

PR opened to fix the formatting: #552

Single-line change — a long assert.equal call in unitTests/resources/subscriptionReplay.test.js was wrapped to conform to Prettier's line-length limit. npm run format:check passes after the fix.