fix: align OpenAPI events limit max with code constant (500 -> 200)

[CHKM001]

PR #814 Fix OpenAPI events limit max mismatch (500 → 200)

Problem

GET /v1/streams/{streamId}/events documented limit parameter with maximum: 500 in stream.routes.ts:94, but the runtime code in events.routes.ts:24 defines MAX_EVENTS_PAGE_SIZE = 200 and the controller clamps to that value. A client requesting limit=400 would silently receive at most 200 rows, contradicting the published contract.

Change

• backend/src/routes/v1/stream.routes.ts:94-95 — Changed maximum: 500 → maximum: 200 and max: 500 → max: 200 in the description to match MAX_EVENTS_PAGE_SIZE.

Verification

The /api-docs.json endpoint is generated dynamically from the JSDoc annotations via swagger-jsdoc, so the corrected value will appear automatically.

Closes #814

[CHKM001]

@ogazboiz ready...

[ogazboiz]

your branch is green, but it went conflicting after the ci fixes landed on main: #969 and #974 touched backend/Dockerfile and backend/src/workers/soroban-event-worker.ts, which this pr also edits. please rebase on main and it should be good to go: git fetch origin && git rebase origin/main && git push --force-with-lease. if any of your Dockerfile or soroban-event-worker changes overlap what #969 already did (copying prisma/ into the runner, and the import type { Prisma } from '../generated/prisma' fix), drop those now-redundant bits and keep just your actual change. i'll re-review and merge once it's rebased and ci is green.

[CHKM001]

okay thank you will hash it out in a bit

[CHKM001]

@ogazboiz I have done it as requested. Please merge!

[ogazboiz]

verified: the code enforces MAX_EVENTS_PAGE_SIZE = 200, but the openapi doc said max 500. this aligns the doc to the actual code constant (500 -> 200). correct. merging.