Upgrade databricks-sql-kernel to 1.0.0

[vuanhphung]

Upgrades the optional kernel backend dependency from 0.2.0 to 1.0.0 and refreshes the lockfile metadata and hashes. The ^1.0.0 constraint allows compatible 1.x releases while keeping the next major upgrade explicit.

Tests: 187 kernel-focused tests passed, poetry check --lock passed, and the connector wheel built successfully.

---

This PR was created with GitHub MCP.

[peco-review-bot]

Verdict: 1 Low

Straightforward dependency bump of the optional databricks-sql-kernel backend from ^0.2.0 to ^1.0.0 with refreshed lockfile hashes. The gating stays correct (kwargs are gated by runtime introspection, not version; connector Python floor remains ^3.10), and the removed pyarrow/3.8-3.9 comments are appropriately obsolete. One low: explanatory docstrings in backend/kernel/client.py still reference the old ^0.2.0 pin.

Other findings

• 🔵 Low — These docstrings still describe the pinned kernel as ^0.2.0 ("whose Session accepts none of them", "the pinned ^0.2.0 wheel ... predates phase 7"), but pyproject.toml now pins databricks-sql-kernel = ^1.0.0. The gating itself is runtime-based (_kernel_session_accepts_kwarg introspects the installed Session constructor), so behavior is unaffected — but the comments now misstate the actual floor and the rationale ("predates phase 7") no longer holds for a 1.0.0 wheel. Consider updating these three references to ^1.0.0 (also lines 165 and 184) so the explanatory comments match the new pin.

[peco-review-bot]

✅ No issues identified by the review bot.