Feature Request: "Fetch All Rows" action in the Query Result grid

[yDiony]

Summary

Add an explicit "Fetch All Rows" action to the Query Result grid, so the whole
result set can be brought into the grid with a single action — equivalent to the
Fetch All / last-record button in PL/SQL Developer, and to Ctrl+End in SQL
Developer desktop.

Current behavior

The Query Result grid fetches rows in batches as the user scrolls. There is no
way to force a full fetch:

• Ctrl+End moves to the bottom of the rows fetched so far and triggers one
  additional batch. It has to be pressed repeatedly, and it is not obvious when
  the end has actually been reached.
• Ctrl+A inside the grid only selects the rows already fetched (about 100 in my
  case); it does not pull the rest of the result set.
• There is no toolbar button, context-menu entry or Command Palette command for
  a full fetch.
• There is no "All rows fetched" indicator and no total row count, so the user
  cannot tell whether the grid is complete.

Steps to reproduce

1. Open a SQL Worksheet attached to a connection.
2. Run a query returning several thousand rows with Ctrl+Enter (Run Statement).
3. Try to bring the complete result set into the grid.

Expected behavior

• A "Fetch All Rows" command available from the Query Result grid toolbar, from
  the grid context menu and from the Command Palette.
• While fetching, a progress indicator and the ability to cancel.
• When finished, a clear indication that all rows have been fetched, plus the
  total row count.

Why this matters

Reviewing a complete result set is a routine task: checking data quality,
copying the full grid into a spreadsheet, or simply confirming how many rows a
statement returns. Today the alternatives are exporting the result, running the
statement as a script (F5, plain text output only), or re-running it through
SQLcl — all of them re-execute the query or move the user out of the grid, which
is exactly what the grid is there to avoid. Both PL/SQL Developer and SQL
Developer desktop have offered this for years, and users migrating to the VS
Code extension notice its absence immediately.

Additional notes

• Related to Feature Request: Implement Pagination in Data Viewer for Improved Performance #8, which discusses the fetching policy of the data viewer from the
  opposite angle (too many rows fetched at once). A configurable batch size plus
  an explicit "Fetch All" would address both cases.
• A companion preference for the worksheet grid batch size (similar to "SQL
  Array Fetch Size" in SQL Developer desktop) would be welcome; today only
  "Folders Fetch Size" is exposed, and it applies to the connections tree.

Environment

• Oracle SQL Developer Extension for VSCode: 26.2.1
• VS Code: 1.138.0
• OS: Windows 11 x64
• Oracle Database: 24.2.11