Add pool transactions infinite loading

[joungminsung]

Summary

• Adds a PoolTransactions section below the pool stats table.
• Loads pool activity from existing Pool contract events: deposits, withdrawals, pay-ins, and payouts.
• Supports incremental older-block loading via scroll/load-more behavior instead of a fixed 100-item cap.
• Shows clearer transaction context: type, asset, amount, pool balance, buffer, market/user, timestamp, and tx link.

Notes

• This avoids assuming a new /pool/transactions backend endpoint.
• The pool transaction reader prefers the configured public Arbitrum fallback RPC for historical event-log reads, but now falls back to the default provider path if that fallback RPC or DataStore lookup fails.
• RPC log calls are bounded by a 9,999 block window and per-filter timeout so the UI reaches an empty/load-more state instead of hanging on slow providers.

Validation

• git diff --check origin/main...HEAD
• npm run build
• Browser checked /pool locally: the new table renders, empty state appears when the current scanned block range has no events, and Load older transactions remains available.

External check status

• The Vercel status check currently links to Vercel's account deployment blocked page, which appears unrelated to this PR's local build result.

Fixes #29

[joungminsung]

Local validation update for latest commit a5fdbdb: git diff --check origin/main...HEAD passes and npm run build passes locally.

The latest commit hardens the pool transaction reader so that if the configured public fallback RPC or DataStore lookup fails while preparing historical event-log reads, it logs the failure and falls back to the default provider path instead of failing the whole table load. The implementation still avoids assuming a new backend /pool/transactions endpoint and keeps the event-log reads bounded by the configured block window/timeouts.

The current Vercel check still points to Vercel’s account deployment blocked page, so it appears to be an external deployment/account restriction rather than a build failure from this PR. I can address any maintainer-requested changes if the implementation needs adjustment.