Release Simple DB 0.1.4 with advanced SQL navigation

[suzdalenko-dev]

What changed

• Release Simple DB 0.1.4.
• Reduce the SQL editor context menu to the daily workflow: Select / Change Connection, Run Statement, Run Script, Go to Definition, and Go to Declaration.
• Add Create New Connection directly to the SQL-file connection picker; Ctrl+Enter uses the same picker when a file has no attached profile.
• Make Oracle Go to Declaration target a package specification while Go to Definition targets the matching package-body implementation.
• Resolve table aliases/columns such as c.nombre -> clientes.nombre.
• Make PostgreSQL and Oracle overload navigation argument-aware; when several candidates remain valid, return/show all of them instead of selecting the first one.
• Follow resolvable Oracle and SQL Server synonyms to their source object, with private Oracle synonyms preferred over public synonyms.
• Preserve connection/database/schema context inside read-only definition documents so F12/navigation can continue from one database object into the next.
• Report explicitly when an object exists but its source/DDL is unavailable because of catalog/source visibility or permissions.
• Hide context-only administrative/object commands from the Command Palette.
• Use Ctrl+Enter for Run Statement, F5 for Run Script, and F12 for Go to Definition in SQL editors.

Why

0.1.3 introduced database-backed Definition/Declaration navigation but both actions used the same path, Oracle package members could stop on the first occurrence, overloads could be chosen arbitrarily, aliases and synonyms were incomplete, and navigation stopped after opening a virtual database definition. 0.1.4 turns that foundation into a predictable database-IDE navigation workflow while keeping connection/execution simple.

User impact

• Any regular .sql file keeps the existing attached-profile workflow and can now create/select a connection from the same picker.
• Oracle package declaration and implementation navigation are distinct.
• Aliased columns, overloads, synonyms, routines, views, tables, triggers, types, sequences, indexes, and other adapter-backed source/DDL objects use the attached database context.
• Read-only database definitions remain navigable.
• Ambiguity is surfaced to the user rather than guessed.

Validation

• Based directly on main commit e05e2a90815783691b41d983575c6896613a58dd.
• The Git tree prepared on GitHub exactly matches the locally validated tree 266a8ffaa775b9f939bb3c66a76e937a6b17384e.
• ESLint passes.
• 15/15 test files pass; 75/75 tests pass.
• Real SQLite adapter/navigation integration passes.
• SIMPLE_DB_LIVE_ENGINES=sqlite npm run test:live-navigation passes.
• A read-only npm run test:live-navigation harness is included for real PostgreSQL, MySQL, SQL Server, and Oracle profiles. Those four network engines were not executed against live servers in this environment because no real connection profiles/credentials are available.
• npm audit --omit=dev: 0 vulnerabilities.
• npm run package succeeds and produces simple-db-suzdalenko-0.1.4.vsix (9.19 MB).