Add support for pagination of data to avoid RPC errors due to responses being too large.

[cryptobench]

While working on the CoinMarketCap clone, I ran into a limitation when trying to display data for the top 100 coins on the homepage.

Fetching data for more than around 30 coins resulted in a failed RPC call due to response size limits:

HttpRequestError: HTTP request failed.

Status: 500  
URL: https://kaolin.holesky.golem-base.io/rpc  
Request body: {"method":"golembase_queryEntities","params":["type=\"CoinHistoricalPrice\""]}

Details: {"code":-32020,"message":"backend response too large"}  
Version: viem@2.31.4

I later found out the response size limit is 5 MB.

To address this, there needs to be support for pagination or batching so I can query the data in smaller chunks and combine it on the client side. This would make it possible to fetch all relevant data without hitting the size limit.

Without a solution to this problem, I basically know there's all the data I need in there, but I have no way to retrieve it.

[krzysiekfonal]

Yes, pagination is one of the crucial part of queries but currently not supported yet in the core -> GolemBase itself and SDK cannot do anything here unless this is supported on GolemBase. We can open issue also there for tracking but it is, however, the issue we are discussing intensively right now (possible solutions of query engine, cause it comes with some cost and with a few alternatives, but we are sure it needs to be done).

However, this issue we can keep to remember to change it on SDK side as soon as GolemBase is ready.