Fix #804: Stop pause/resume controllers from duplicating PAUSED/RESUMED events

[Banx17]

Overview

This PR fixes issue #804 by stopping the stream.controller.ts from creating synthetic PAUSED and RESUMED events in the database when a stream is paused or resumed. Previously, the controllers would persist these events with a placeholder transaction hash, which led to duplicate history rows when the real on-chain event was indexed by SorobanEventWorker. Now, the state updates are fully delegated to the indexer, ensuring exactly one source of truth.

Related Issue

Closes #804

Changes

• stream.controller.ts: Removed prisma.stream.update and prisma.streamEvent.create in pauseStream and resumeStream handlers.
• tests: Added pause-resume.regression.test.ts to assert that pauseStream controller no longer modifies the DB, and exactly one PAUSED row is created by the indexer.
• tests: Updated integration tests in stream-actions.test.ts to reflect the removed database mutation expectations.

Verification

npm run lint ✅ completed (existing repo warnings only)
npm run typecheck ✅ passed
npm test -- tests/integration/pause-resume.regression.test.ts ✅ passed
npm run build ✅ passed

[ogazboiz]

nice root-cause fix for #804. the pause/resume controllers were double-writing: they did stream.update + streamEvent.create, but the soroban-event-worker indexer already handles the stream_paused/stream_resumed on-chain events with the same writes, so every pause/resume produced duplicate db state (and the controller's event used ledgerSequence 0 + the simulated txHash, not the real on-chain values). now the controllers only simulate and return the existing stream, leaving persistence to the indexer as the single source of truth, and the regression test asserts the controller doesn't call update/create while the worker writes exactly one PAUSED upsert with the real tx hash. merging.