Enhance Paging/Pagination

[JerryNixon]

Combining these issues to start a discussion:

• [Enhancement]: Provide $top as a synonym for $first in REST #2474 "Add $top synonym"
• No totalCount for pagination? #2234 "Add totalCount"
• Add alternative support for `Skip` parameter to facilitate flexible navigation within small datasets #1927 "Add skip"
• Add properties to queries (i.e. add "TotalCount") #1912 "Add TotalCount"
• How to handle forward and backward pagination properly with GraphQL #2088 "Forward & back navigation"
• [Enhancement]: Page by index #2460 "Page by index"
• [Enhancement]: Pagination metadata #2459 "Add metadata"
• [Enhancement]: Add $skip, $take, and $count #2369 "Add skip, take, count"
• [Bug]: GraphQL pagination with order by statements omits values #2274 "Page with OrderBy"
• [Enhancement]: $first & $after keywords in REST & GQL #2246 "Add first and after"
• [Enhancement]: hasPreviousPage / Before Cursor not found #2238 "Add hasPreviousPage"
• Optimize how the additional row in paginated result is chopped off #1433 "Optimize page chop off"
• Aggregate count #1429 "Add Count"

Pagination is not part of the current milestone, but I think we should work it out to be in the next.

References

• Pagination documentation

{
  "runtime": {
    "pagination": {
      "max-page-size": <integer; default: 100000>,
      "default-page-size": <integer; default: 100>
    }
  }
}

Output:

{
  "value": [
    {
      "id": 1000,
      "title": "Prelude to Foundation"
    }
  ],
  "nextLink": "https://localhost:5001/api/books?$after=W3siRW50aXR5TmFtZSI6ImJvb2tzIiwiRmllbGROYW1lI=="
}

Questions

1. Do we configure the default paging style?
2. Do we change the nextLink structure somehow?
3. Do we support this in both REST & GQL?
4. Are aggregates too expensive to calculate?