perf(frontend): add stable pagination and filtering for stream history

[arisu6804]

Problem

History pages duplicate or omit records while new stream events arrive and become slow at scale.

Objective

Deliver a production-quality improvement to stream history tables, filters, and pagination that creates measurable value for correctness, security, reliability, performance, or maintainability.

Implementation scope

• Use cursor/snapshot pagination; define stable sort and filters; cancel obsolete requests and cap page size.

Acceptance criteria

• No duplicates or gaps occur under inserts; filters are reflected in cursors; requests remain bounded.

Required validation

• Pagination race, filter contract, cancellation, and large-fixture tests.
• Existing tests and CI remain passing.
• Add regression coverage for the original failure mode.
• Do not weaken, delete, or skip unrelated tests to obtain a green build.

PR quality bar

• Keep the PR focused and explain design tradeoffs, compatibility impact, and test evidence.
• Avoid typo-only, documentation-only, cosmetic-only, or unrelated refactor submissions.

Out of scope

• Broad rewrites not required by the acceptance criteria.
• Changes to unrelated services, contracts, or user flows.

[grantfox-oss]

🦊 GrantFox — @euniceamoni has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #134)
2. Your PR will be reviewed by the StreamPay-Organization maintainers

Good luck! Track your progress on GrantFox.