Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

refactor(admin): share the server table query state and load-more latch

The load-more latch was copied into all eleven server tables and the
copies had already drifted: six guarded on isError but swallowed the
failure, five logged it but retried on every further scroll. useLoadMore
takes the union, so neither half regresses.

useServerTableQuery comes from fix/admin-ui-followups unchanged, so this is
the hook that branch already carries rather than a second one. It absorbs
three different query-state shapes:

- six org tabs held state, a memo and a debounce by hand
- the org, user and invoice lists debounced the table state itself, so the
  grid lagged behind typing; only the request is debounced now, and the
  invoice list gains the debounce it never had
- audit logs and project members kept query and rqlRequest in one object;
  audit logs still publishes its request for the navbar's CSV export, now
  from an effect, and project members drops sort through mapQuery

The apis tab also starts resetting offset when the query changes, which the
other ten already did.

Eleven views, 223 lines lighter.