Support cursor-based pagination for any contract function returning unbounded collections

[phertyameen]

Location

contracts/*/src/lib.rs

Problem

Any read function that could return a list whose size grows unboundedly over the contract's lifetime (e.g. an event/history log, if one exists or is added by other proposed issues) risks failing due to resource limits once the underlying data grows large enough, unless it supports paginated/cursor-based retrieval from the start.

Acceptance Criteria

• Every current and near-term-planned list-returning function audited for unbounded growth risk
• Pagination (cursor or offset-based, consistent with Soroban idioms) implemented for any function found at risk
• Documented as a required pattern for any new list-returning function added by future contract work, including the 20 previously-proposed new contracts

[Iker2522]

I can audit all list-returning functions across contracts/*/src/lib.rs and introduce Soroban-idiomatic cursor or offset-based pagination to prevent unbounded storage and execution failures. Additionally, I will update the contract documentation to mandate pagination patterns for all future list-returning methods. I can submit a PR within 1 to 2 days.