Connections should not use Skip(...)/Take(...), which are translated to OFFSET/LIMIT, for paging

### Description

As for now, connections use Skip(...)/Take(...) for fetching particular page. It's not performant way for last pages - the further page from start the less performant a final query is.

### Describe the solution you'd like

Another approach for pagination is to use compound cursor consisting of id and (probably) other fields if additional sorting is applied.
Instead of sql `OFFSET`/`LIMIT` it should be translated to `WHERE Id > @id ORDER BY Id LIMIT @size` (or to `WHERE Name > @name AND Id > @id ORDER BY Name, Id LIMIT @size` with additional sorting by name field).

Start by locating the connection pagination code that currently applies Skip(...)/Take(...), then trace how its SQL query and sorting are built. Done means replacing OFFSET/LIMIT paging with compound-cursor paging, including the additional sorting-field case described in the issue. The payload names no files or tests.

Written by the indexing model from the issue text.