fix(pagination): cursor-driven paginate to stop duplicate page fetches (Closes #403)

[foxxx009]

Closes #403

Problem

paginate() in src/pagination.ts:46-77 built a fresh { limit } query on every loop iteration and never read cursor metadata from the response, so a page containing exactly limit items was re-requested until maxPages, yielding the same items repeatedly. The sibling helpers parseCursorPage and buildPaginationQuery (same file) were never called by paginate, and tests/pagination-helper.test.ts explicitly asserted the duplicate behavior (6 yielded items for a single-page dataset).

Changes

src/pagination.ts

• paginate() now accepts a fetchPage that returns CursorPage<T> (items + nextCursor + hasMore) instead of a bare array
• The returned nextCursor is fed back through buildPaginationQuery for the next request; the first call carries only the limit
• Iteration stops when nextCursor is null/empty, hasMore is false, a page is shorter than limit (when limit is set), or maxPages is reached

tests/pagination-helper.test.ts

• Removed the test asserting the duplicate-page behavior
• Added 7 cursor-driven cases: two-page dataset (asserts first call has no cursor and second call receives { cursor: 'c1' }), no-duplicate guarantee for a full page, maxPages stop while cursors keep coming, empty page, short page, hasMore: false stop, single cursor-less page

Verification

• npx vitest run tests/pagination-helper.test.ts — 16/16 pass
• npm run typecheck — clean
• npm run test:unit — 873 passed, only the 4 pre-existing Windows path-resolution failures in exports-subpath-resolves / tree-shaking remain (zero new failures vs. baseline)
• prettier --check and eslint clean on both touched files