fix(cql console): mark pagination counter as partial while server has more rows

[digiserg]

Summary

• Tabulator's built-in paginationCounter: 'rows' only counts rows currently loaded into the table, so a server-paged SELECT looked "complete" after the first chunk and the total silently grew with every "Next" click.
• Adds a custom paginationCounter in renderer/js/utils/core.js that reads a new hasMorePending flag on the Tabulator instance and appends + ... (more available) while the server still has rows to fetch, switching to the exact count once isOutputCompleted is true.
• events-get-connections.js now sets tabulatorObject.hasMorePending at table creation and on every subsequent page append, from the existing isOutputWithPaging/isOutputCompleted state (no change to IPC shapes or fetch mechanics).

Fixes #1082

Test plan

• node --check on both changed files
• Isolated jsdom test of the new paginationCounter function confirms distinct text for pending vs. complete vs. empty states
• Manual click-through against a live cluster with a 300+ row table (not run in this session — no cluster available here)

Assisted-by: Claude Code