Add game pagination to DatabaseReplayProvider

[vinceau]

Description

This PR adds pagination support when fetching games.

How it works

1. When fetching from the database, fetch limit + 1 items.

This allows us to determine if we actually have any more items to return, in order to populate the continuation token. If this string is populated, there are more records to come. If there is no continuation token, all records have been fetched.

2. Take the last item returned from the records and encode it into a continuation token.

We need to be able to refer to each item in the list of records, in a deterministicly sorted order. We do this by taking the key that it's sorted by e.g. game start time, and the record ID, and when returning results always sort by these two columns. We return the continuation token in the base64 encoded form of ${value},${lastRecordId}.

3. When fetching more items, pass the previous continuation token.

The continuation token is decoded back into the order by key in order to re-fetch the previous query, and using a specially crafted where-clause to start from the expected record (the limit + 1 record from before). The frontend renderer is responsible for storing and re-sending the continuation token as needed.

Resources

Here are some resources which I found useful when implementing pagination.

• Web API Pagination with the 'Timestamp_ID' Continuation Token
• How to Implement Cursor Pagination Like a Pro
• Cursor based pagination with arbitrary ordering
• The best database pagination technique is...
• Pagination with Relative Cursors
• Offset and keyset pagination with Kysely