going over the queryLimit result has a breaking change in v5. But should it be allowed at all?
Sorry for not following the template, but this is more of a question than a report.

In v4, when I set the rest maxLimit to 100, and I query with pageSize=250 (which is currently the `gatsby-source-strapi` default limit), the result would be 100 entries _from (100 * `page`)_. So 1371 will have 14 pages, and `[pageSize]=250&pagination[page]=13` will actually hold items 1301-1371

In v5, when I set the rest maxLimit to 100, and I query with pageSize=250 (which is currently the `gatsby-source-strapi` default limit), the result would be 100 entries _from (250 * `page`)_. After the 7th page, `pagination[pageSize]=250&pagination[page]=7`, there will be zero items, as it starts getting item 1500. 
To make things more interesting, the response `meta.pagination.page` actually sees i'm going over the limit, as it returns 16 (we were requesting page 7):
```
{
    "data": [],
    "meta": {
        "pagination": {
            "page": 16,
            "pageSize": 100,
            "pageCount": 14,
            "total": 1367
        }
    }
}
```
    
This raises the question, should the REST call not crash on going over the limit? Because the response will not be what I am asking, so I'd rather have no response than a bad response. I just learned that the hard way the past 2 days...

**tl;dr
going over the rest maxLimit is flaky. Can we please make it crash?**
