fix(server): advance campaign to InProduction on first tranche release (#173)

[trenysx]

Summary

Closes #173

Per the escrow contract's state machine, the first tranche release transitions a campaign from Funded to InProduction (see release_tranche in contracts/production_escrow/src/lib.rs, which accepts both Funded and InProduction). The indexer's handleTrancheReleased only created a Tranche row and upserted the recipient user, leaving Campaign.status stuck at Funded until HarvestReported fired.

Change

In server/src/indexer/parsers/event-parser.service.ts, handleTrancheReleased now performs a conditional updateMany that advances status to InProduction only when the current stored status is Funded:

• where: { id: campaignId, status: 'Funded' }
• data: { status: 'InProduction' }

Because the where clause includes the current status, a second/third tranche release on an already-InProduction campaign matches zero rows and is a no-op rather than an unnecessary write.

Tests

Added a TrancheReleased -> InProduction status block to event-parser.service.spec.ts:

1. First release flips a Funded campaign to InProduction (asserts the exact conditional update call).
2. Two releases are asserted to only ever issue the Funded-guarded update (matching count 0 simulates an already-released campaign), proving later releases cannot reset or duplicate-write the status.

All 47 unit tests in event-parser.service.spec.ts pass; tsc --noEmit and eslint are clean for the changed files.