Add batch query and proper pagination

Is your feature request related to a problem? Please describe.

Currently, the tables is limited to returning 65535 entries per table due to PostgreSQL.
This results in larger tables being unviewable in the browser.

Describe the solution you'd like

Implement batch querying with a limit that respects PostgreSQL's query limitations.
Instead of attempting to query the entire table at once, it should rather index how many rows are in the database to make up the pagination number, and then query the entries related to that page.
This will result in less spontanious resource usage for the server, and prevent breaching the query limit.

Describe alternatives you've considered

Haven't tried any solutions other than doing limited API calls through external applications. This is in reference to using Tables on the WebUI of Nextcloud. Only workaround is creating multiple views, one for every 65535 table entries.

Additional context

No response

The issue names no files or tests; start by tracing how the Tables WebUI loads table rows and how PostgreSQL queries supply pagination data. Define the existing pagination and API behavior first, then verify that tables larger than 65,535 rows can be browsed using bounded batches without excessive server resource usage.