fix: drop before cursor on follow-up autoPagination requests

[tribble]

I hit the API's Please provide either "after" or "before" parameters. error when calling autoPagination() on a list fetched with before: the first follow-up request re-sends the stale before alongside the new after cursor, and the API rejects any request carrying both.

• Follow-up auto-pagination requests no longer re-send the caller's before; they send only after (the previous page's listMetadata.after), so a walk started from a before cursor pages forward instead of failing on the second request.

Test plan

Red-first regression in src/common/utils/pagination.spec.ts ("paginates forward from a before cursor, dropping before on follow-up requests"), starting from {before: 'u21'}:

• On main (3b1e398) it fails: follow-up call 2 goes out as {after: 'u12', before: 'u21', limit: 100} and call 3 as {after: 'u14', before: 'u21', limit: 100} — the both-cursors request the API rejects.
• With the fix it passes: call 1 is {limit: 100, before: 'u21'}, follow-ups are {limit: 100, after: 'u12'} and {limit: 100, after: 'u14'} with no before, and the walk returns the three pages concatenated in order (u11, u12, u13, u14, u15).

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no outstanding finding or new actionable issue was established.

Summary

The PR changes auto-pagination started with a before cursor to use that cursor only on the initial request, then continue with each page’s after cursor. The regression test checks the request sequence and resulting item order.

_{Reviews (2) · Last reviewed commit: "fix: keep autoPagination forward-only af..." · Reviewed by Greptile}