Incorrect Pagination leading to missing results

**Describe the bug**
Missing data due to Incorrect pagination.

**To Reproduce**
Steps to reproduce the behavior:
- Query any subgraph which has e.g. a `timestamp` and should return > 1800 entities.
- After the first pagination, instead of using `"skip: 1800"` and `"first: 900"`
- in my case it uses `"skip: 0", "first: 900"` and `"timestamp_gt: $lastOrderingValue0"`.
- If the timestamp of result with index 1800 is the same as 1801, this will skip 1801 and any other events which happen to have the same timestamp as index 1800.

**Expected behavior**
Results with same timestamp as the last returned timestamp from the previous result set of the pagination are present.

> Sorry I'm not experienced enough with the library to understand how it determines over which field to paginate - a briefer summary is that pagination shouldn't occur over fields which are not guaranteed to be unique.

*Originally from: [roama3](https://github.com/roama3)*