fix(api-server): page token transactions by offset instead of cursor

[nullPointerEnjoyer]

Summary

• Port of fix(api-server): page token transactions by offset instead of cursor #2135 to master (same bug exists here): GET /api/v2/token/{id}/transactions returned an
  empty page for every token, because the route passes the request's page offset (skip-N, default 0)
  while the storage layer interpreted the parameter as a cursor (WHERE tx_global_index < $2).
• Align the storage layer with the skip-N semantics the HTTP API uses: newest-first list, offset
  entries skipped, empty page at or past the end. Trait parameter renamed to offset across the
  trait, both backends, and wrappers.
• Guard oversized offsets uniformly: an offset too big for a bigint is past the end of any result
  set, so postgres returns an empty page (five queries previously wrapped as i64, yielding 500s);
  the in-memory backend skips by usize::MAX instead of truncating as usize (seven queries),
  which also fixes first-page-instead-of-empty-page wraps on narrow-pointer targets.
• Cherry-picked from release-v1.4.1 with conflict resolutions where master's pool/order listings
  diverged (sort and balance-decode rework); behavior of other endpoints unchanged.

Test plan

• New storage-level regression test token_transactions_offset_paging (both backends): default
  page starts at the newest transaction, offset skips entries, offsets at/past the end (u64::MAX and
  1<<35) yield an empty page instead of an error.
• Existing storage tests updated to the offset semantics; in-memory suite green.
• ./do_checks.sh green; OCR review clean.

[github-actions]

🔍 OpenCodeReview found 1 issue(s) in this PR.

• ✅ Successfully posted inline: 0 comment(s)
• 📋 Routed to summary by policy: 1 comment(s)

---

📄 api-server/storage-test-suite/src/basic.rs (L2771-L2774)

⚠️ GitHub could not post this as an inline comment: Routed to summary (severity low · category test)

All reads here go through the same read-write transaction (tx) that performed the writes, so this only exercises within-transaction visibility. Consider asserting at least one page after tx.commit() via a fresh read-only transaction, to verify the offset paging also works against committed state in both backends.

💡 Suggested Change

Before:

    tx.commit().await.unwrap();

    Ok(())
}

After:

    tx.commit().await.unwrap();

    // Verify offset paging against committed state via a read-only transaction.
    let ro = storage.transaction_ro().await.unwrap();
    assert!(ro.get_token_transactions(token_id, 10, 10).await.unwrap().is_empty());
    assert_eq!(ro.get_token_transactions(token_id, 4, 3).await.unwrap(), &newest_first[3..7]);

    Ok(())
}