Update to hotdata SDK 0.2.0 and follow truncated query results

[zfarrell]

Bumps the hotdata Rust SDK to 0.2.0 and handles its new truncation contract: a fast-completing but large query returns an inline 200 with truncated = true and only a preview, so the inline branch now follows result_id to the full result via the same Arrow path the async branch uses (falling back to the preview with a warning when no result_id is present).

[claude]

nit: following a truncated inline response to Arrow silently drops the inline response's warning (and execution_time_ms). fetch_arrow_result → arrow_result_to_query_response hardcodes warning: None / execution_time_ms: None, so a query-level warning that the server attached to a truncated-but-persisted result won't reach the user. If that warning is meaningful here, consider carrying resp.warning.flatten() through to the fetched result. (not blocking)

[zfarrell]

Good catch — fixed in 579135b. The Some(result_id) arm now carries resp.warning and execution_time_ms onto the fetched Arrow result, with a test asserting both survive the follow.

[claude]

Clean handling of the new truncation contract. The resolve_inline branching (non-truncated → as-is, truncated+result_id → Arrow follow, truncated+no result_id → preview with warning) is sound, and the tests cover all three paths plus warning preservation. One non-blocking nit left inline.

[codecov]

Codecov Report

❌ Patch coverage is 99.02913% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/query.rs	99.02%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[claude]

Prior nit resolved (warning + execution_time_ms now carried through the Arrow follow, with a test asserting both survive). Logic is correct across all three branches, conversions are consistent with the existing inline path, and the fallback warning appends rather than clobbers. Tests are meaningful. LGTM.