fix: resolve assigned stream and CI issues

[0takuc0mrade]

Summary

• clean up each signTx session abort listener on every exit path
• show ended-stream claimable balances and stop RateTicker at endTime
• regenerate the npm lockfile from the official registry and immutable HTTPS SDK archive
• reject npmmirror.com lockfile entries in CI
• repair the incomplete fix(create,stream,lib): correct stream rate, recipient guard, stream ID, and deposit total #379 merge artifacts exposed after npm ci was restored

Verification

• npm ci
• npm run lint
• npm run typecheck
• npm test (413 passed, 4 todo)
• npm run build

Fixes #374
Fixes #375
Fixes #376
Fixes #404

[drips-wave]

@0takuc0mrade Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[mhikel66]

Heads-up: fixing the lockfile is necessary but not sufficient for a green npm ci. @conduit-protocol/sdk is a git dependency with a prepare build, and conduit-protocol/streamFi-sdk main currently doesn't compile — its #498 merge reintroduced _signer(): Signer without the Signer type import (TS2304). So npm ci fails at the SDK's prepare step regardless of registry URLs. That's fixed in conduit-protocol/streamFi-sdk#555 — this repo's CI needs both.

[Jaydbrown]

This branch is far behind main — merging it produces 10 conflicting files (package.json/package-lock.json, contexts/WalletContext.tsx, .github/workflows/ci.yml, app/stream/[id]/page.tsx, the test suite) and a 40-file / ~600-line divergence, reverting the shared withTimeout extraction and the #363 recipient-check test scaffolding. Needs a fresh rebase onto current main. Leaving open per instruction.