fix(tanstack-query): propagate TPageParam generic through useInfiniteFindMany

[Copilot]

TPageParam was not threaded through useInfiniteFindMany (and suspense variants), causing lastPageParam, pageParams, and getNextPageParam callback parameters to fall back to unknown regardless of what the user provided.

Changes

• ModelInfiniteQueryOptions<T, TPageParam> – added TPageParam = unknown generic and forwarded it to the underlying UseInfiniteQueryOptions (positions 4 & 5), in all three adapters (React, Vue, Svelte)
• ModelSuspenseInfiniteQueryOptions<T, TPageParam> – same treatment for the React suspense variant
• useInfiniteFindMany / useSuspenseInfiniteFindMany interface signatures – added TPageParam = unknown so TypeScript can infer the page param type from the getNextPageParam callback
• useInternalInfiniteQuery / useInternalSuspenseInfiniteQuery – updated generics and cast initialPageParam: args as TPageParam (args is unknown at the impl level but always matches at the call site)

Before / After

// Before: lastPageParam and pageParams are unknown
const result = client.user.useInfiniteFindMany({}, {
    getNextPageParam: (_last, _all, lastPageParam) => lastPageParam, // lastPageParam: unknown
});
result.data?.pageParams[0]?.cursor; // TS error — unknown has no .cursor

// After: TPageParam is inferred from the callback signature
const result = client.user.useInfiniteFindMany({}, {
    getNextPageParam: (_last, _all, lastPageParam: { cursor: string }) => lastPageParam,
});
result.data?.pageParams[0]?.cursor; // ✓ string

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.