Db pagination for tabular reviews

From the PR description

Summary

For the Tabular Reviews page, this moves the keyword search and order by functions from the data table into the backend, and adds pagination with lazy load fetching.

Why / Motivation

First part of the pagination feature request from the discord chat.

Changes

Implement offset based paging in the database for the tabular view.

Tradeoffs & risks

Considered multiple UI paging strategies and interface options, against the potential perf impacts and scope for the number of records considering this is an open source project and may be used in multi-tenanted environments.

This is an implementation on a single view, and once the approach is reviewed and approved, should be mirrored in the other views which require paging.

How verified

Added some tests, but mainly by manual testing in my local instance manually populated with seed data to test pagination.

Checklist

• Ran the relevant build/test command for the area changed.
• Reviewed git diff and removed unrelated changes.
• Updated docs / env examples if setup, config, or behavior changed.
• No secrets, API keys, real documents, or .env files committed.