Problem

There is currently a massive functional and visual disparity between how tabular data is rendered in the SQL query editor vs. when opening a table from the connection schema tree:

When a user runs SELECT * FROM users in the SQL editor, they get a powerful, modern desktop grid. But when clicking users in the schema tree, they get an outdated, limited view without any of these capabilities.

Proposed Solution

Refactor SqliteTableView, PostgresTableView, and ExtensionTableView to reuse VirtualResultGrid (or ResultsTab with read-only/read-write modes):

• Provide virtualized 2D scrolling and auto-fit columns for all schema tables.
• Enable selection stats (DataGridCalcBar), quick filtering (DataGridFilterBar), and the cell inspector across all table browsing views.
• Unify pagination into either infinite scroll or a standardized footer strip that matches ResultsTab.

Acceptance Criteria

• Schema table views share the same grid component and visual capabilities as SQL query results
• Users can resize columns, filter rows, inspect cell payloads, and view selection stats in both views
• Legacy custom table rendering code in sqlite_table_view.dart, postgres_table_view.dart, and extension_table_view.dart is eliminated