feat(ux): bi-directional navigation and breadcrumbs between table views and server stats/sql

[ZhuchkaTriplesix]

Motivation & Problem

Currently, in PostgreSQL, MySQL, SQLite, and Extension workspaces, navigating from a table view back to Server Stats or the SQL workspace is a dead end:

• Inside PostgresTableView / MysqlTableView / SqliteTableView, there is no header breadcrumb or button to open Server Statistics or the root workspace.
• The only way to reach Server Stats is by clicking the root connection node in the sidebar tree.
• When clicking the root connection, MainScreenWorkspaceState.selectConnection clears the selected object (selectedPostgresObject = null, etc.), completely forgetting the last visited table.
• To return to the table, users must re-expand and re-locate the table in the sidebar tree. All table transient state (pagination offset, scroll position, custom SQL filter) is lost upon unmounting.
• In addition, table toolbar pagination buttons are labeled Back and Next (Text('Back')), which users frequently confuse with browser-like screen navigation (and it is disabled on page 1).

Proposed Scope & Fluid Motion

1. Breadcrumbs / Navigation Bar in Table Views:
   • Introduce an interactive breadcrumb or header strip in table toolbars: [Connection] › [Database / Schema] › [Table Name].
   • Clicking the Connection or Schema chip navigates back to Server Stats / SQL workspace.
2. Table Pagination Label Fix:
   • Rename Back / Next in PostgresTableToolbar, MysqlTableView, and SqliteTableView to ‹ Prev and Next › (or chevron icons) to disambiguate pagination from screen navigation.
3. Remember Last Visited Object & Quick Return:
   • Track lastSelectedObject per connection in workspace state.
   • In PostgresWorkspaceHome / MysqlWorkspaceHome, provide a fluid action chip / button: Return to table: <name>.
4. Fluid Motion:
   • Ensure transitions between Table and Server/SQL workspace morph seamlessly using Querya motion tokens (QueryaMotion.standard, 200ms cubic easeOut/easeIn), without visual stutter or layout jumps.

Acceptance Criteria

• Users can navigate from any table/view back to Server Stats or SQL workspace directly from the view.
• Users can easily return to their previous table without re-navigating the entire sidebar tree.
• Pagination buttons no longer use ambiguous 'Back' label.
• Fluid motion complies with QueryaMotionScope (standard 200ms on full, instant on off/reduced).