Gracefully handle huge results

[Nemo64]

The ExecuteStatement documentation warns about huge results.

The response size limit is 1 MB or 1,000 records. If the call returns more than 1 MB of response data or over 1,000 records, the call is terminated.

I tested queries with over 10,000 results and it worked fine but I wouldn't rely on it.

To prepare for the day they actually limit the result, queries should automatically get a LIMIT applied and be paged while iterating the result. The limit should be configurable (including unlimited) but default to 1,000 so the implementation follows the specification.

It may be possible to execute the request for the next page async but I have the experience that guzzle only actually starts the request when accessing it so there needs to be some investigation.