fix: ensure connections are closed after sync operations

[Dozie2001]

• Fix database connection leaks in nao sync — connections opened via db_config.connect() were never closed, exhausting the connection pool across repeated
  syncs or large projects
• Wrap connection usage in try/finally blocks with conn.disconnect() in sync_database(), DatabaseConfig.execute_sql(), and BigQueryConfig.execute_sql()

[cubic-dev-ai]

1 issue found across 4 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="cli/nao_core/commands/sync/providers/databases/provider.py">

<violation number="1" location="cli/nao_core/commands/sync/providers/databases/provider.py:64">
P2: The `try` block should start immediately after `conn = db_config.connect()` to guarantee `conn.disconnect()` runs in the `finally` even if the intervening `console.print(...)` raises. As written, an exception in `console.print` would leak the connection — the exact bug this PR aims to fix.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}