fix: suppress console logging that corrupts TUI display

[anandgupta42]

What does this PR do?

Fixes raw JSON log lines from third-party libraries (e.g. {"level":"INFO","message":"Creating new connection object"}) leaking into the chat UI, corrupting the TUI display. Suppresses console output from 4 sources:

• snowflake-sdk: Winston logger with additionalLogToConsole=true by default → set logLevel: "OFF"
• @databricks/sql: Winston Console transport at info level → create DBSQLLogger with error-only level
• dbt-tools adapter: console.error("[dbt]", msg) on every dbt operation → buffer in memory ring buffer
• Tracing module: console.debug/console.warn on trace errors → route through Log.Default (log file only)

Type of change

• Bug fix (non-breaking change which fixes an issue)

Issue for this PR

Closes #249

How did you verify your code works?

• Confirmed snowflake-sdk and @databricks/sql both use Winston Console transport by default (verified in node_modules source)
• Confirmed dbt-tools adapter writes console.error on every dbt-integration callback
• Confirmed tracing module has 2 console.debug/console.warn calls
• All 5 packages pass turbo typecheck
• Biome lint passes on all changed files

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• New and existing unit tests pass locally with my changes

🤖 Generated with Claude Code

[sentry]

Bug: Error logs from dbt operations are now buffered but never retrieved, as the new getRecentDbtLogs() function is never called. This results in silent failures with no diagnostic output.
_{Severity: HIGH}

Suggested Fix

The code that calls dbt operations and handles their failures (e.g., in tryExecuteViaDbt() or CLI command handlers) must be updated. In the catch blocks or after detecting a failure via stderr, these callers should invoke getRecentDbtLogs() and log the retrieved error messages to provide necessary diagnostic information.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/dbt-tools/src/adapter.ts#L79-L81

Potential issue: The modification to the dbt adapter's `terminal()` function routes all
error logs into an in-memory buffer, `dbtLogBuffer`, instead of `console.error`. While a
new function, `getRecentDbtLogs()`, was added to retrieve these buffered logs, it is
never called anywhere in the codebase. As a result, when any dbt operation fails (e.g.,
in `tryExecuteViaDbt()` or CLI commands), the error messages are silently buffered and
lost. This completely removes error visibility for debugging dbt failures, as the
diagnostic information is never retrieved or displayed to the user or developer.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[anandgupta42]

Addressed in commit 2d36571 — getRecentDbtLogs() is now wired into the bail() error handler in index.ts, so buffered logs are included in diagnostic JSON output on failure. The buffer was also extracted to its own log-buffer.ts module with 7 unit tests.