Support paginated client dataset reads from FWSS

[rjan90]

Support the paginated client dataset query change that landed in filecoin-services#444. That contract change added paginated overloads for client dataset reads plus a length helper, so SDK dataset enumeration should be updated to use that shape instead of assuming the full client dataset list can always be returned in one call.

Context:

• filecoin-services#444
• filecoin-pin#362

This should cover the synapse-core / synapse-sdk client dataset query paths that currently rely on unpaginated reads.

[Chaitu-Tatipamula]

can i take this up? @rjan90

here is a step by step plan that i would like to follow

in synapse-core

• Add the new ABI entries manually (i think the contract isn't deployed yet, so abi generation won't pick them up i believe)
• create new get-client-data-sets-length.ts & getClientDataSetsLength() wrapper
• create new get-client-data-sets-ids.ts & getClientDataSetsIds() wrapper for clientDataSets
• add an optional offset/limit params to the existing getClientDataSets() defaults to unpaginated(returns all like before)

in synapse-sdk

• Expose getClientDataSetsLength() and getClientDataSetsIds() on WarmStorageService
• updae getClientDataSetsWithDetails() to use paginated clientDataSets overload instead of raw contract call

All pagination params can default to 0n to fetch all, so no breaking changes would be introduced and the existing callers stay unaffected

i will also update the mocks, presets and add tests for new functions.

[rvagg]

Don't add new methods in synapse-sdk, just core, then use this to support existing functionality that needs it. Otherwise this seems fine. Refer to the filecoin-pin issue and just make sure we're solving for that in the process here. Also look at other pagination calls in here to see the established patterns and try to be consistent where possible.
Otherwise seems good.

[hugomrdias]

Hi @Chaitu-Tatipamula would be awesome if you can take this up.

Please start with a PR with just synapse-core changes follow the AGENTS.md instructions to create new actions.
Dont update the abi manually, you can just pick them up by change the GIT ref here

synapse-sdk/packages/synapse-core/wagmi.config.ts

Line 8 in 966a389

const GIT_REF = '44ef7165f7db93e5491a27ce14460143ff9a7d13'

After the synapse-core PR we can follow up with synapse-sdk changes if need.

Otherwise your plan seems fine.

Thank you.

[Chaitu-Tatipamula]

thanks for the feedback @rvagg @hugomrdias!

i'll scope the first PR to synapse-core only. i updated the ABI already, ran wagmi generate with the latest git ref d08214e1b3d200e0bc80f0d4f2e5ea3e1e4d603e

i'll just follow for the remaining as i said in previous comment