limit the size of /rows response
See https://github.com/huggingface/moon-landing/pull/2147, and https://github.com/huggingface/moon-landing/pull/2147#issuecomment-1048976581 in particular:

> BTW, I'm thinking I should have implemented this on the backend, not here (or only as a safeguard). Indeed, we already artificially limit to 100 rows on the backend, so why not by the size too.
> 
> Also: it does not make sense here for three reasons, for problematic datasets:
> 
> - why fetch a very large JSON of 100 rows if we will slice it to 0 or 1 row?
> - requesting 100 rows might generate a lot of load to the server to create the JSON
> - if the JSON is really big, the fetch might timeout, which is silly, since it would have been sliced afterward.

limit the size of /rows response: See https://github.com/huggingface/moon-landing/pull/2147, and https://github.com/huggingface/moon-landing/pull/2147#issuecomment-1048976581 in particular:

> BTW, I'm thinking I should have implemented this on the backend, not here (or only as a safeguard). Indeed, we already artificially limit to 100 rows on the backend, so why not by the size too.
> 
> Also: it does not make sense here for three reasons, for problematic datasets:
> 
> - why fetch a very large JSON of 100 rows if we will slice it to 0 or 1 row?
> - requesting 100 rows might generate a lot of load to the server to create the JSON
> - if the JSON is really big, the fetch might timeout, which is silly, since it would have been sliced afterward.
