Auto-paginate GLQL analytics charts past the 100-row page

What does this MR do and why?

Analytics-mode GLQL charts and stat displays rendered only the server's first 100-row page of aggregated data, with no indication anything was missing. A truncated chart looks complete, so it silently misled readers.

They now page through to the connection's count, capped at 1,000 rows, reusing a new fetchNextPage() shared with the existing loadMore(). Charts deliberately get no Load more button — a partially paged aggregate looks complete at every intermediate step, which is worse than the bug. Lists and tables are unchanged. The change event fires once for the whole fetch, so the chart doesn't redraw through incomplete states. A failed continuation page keeps the pages already loaded and goes to Sentry rather than blanking the chart.

The compiler dependency is satisfied. glql!513 (merged) shipped in 0.38.0, and the version bump landed on master separately in f9d0863a, so there is no bump in this MR.

One known gap: there is no user-facing truncation warning — resultsTruncated is emitted but unconsumed. Followed up in glql#216.

References

Issue: glql#170 (closed) Compiler dependency: glql!513 (merged)

Screenshots or screen recordings

Before	After

How to set up and validate locally

Run yarn jest spec/frontend/glql. End-to-end verification needs the compiler dependency built locally.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

🤖 Generated with Claude Code