fix(clickhouse-driver): Respect timezone for origin in custom granula…

[ovr]

Problem

When using custom granularities with an origin timestamp, ClickHouse's dateBin implementation was not respecting time zones properly:

ClickHouse aligns both timestamps internally to the same timezone before computing the difference, causing an unintended offset. As a result, the date difference and the final rounded time are incorrect, and the returned values are effectively in UTC.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.10%. Comparing base (b0b011e) to head (e94bac7).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #10110      +/-   ##
==========================================
- Coverage   78.10%   78.10%   -0.01%     
==========================================
  Files         457      457              
  Lines       90994    90998       +4     
  Branches     3330     3331       +1     
==========================================
+ Hits        71070    71073       +3     
+ Misses      19451    19448       -3     
- Partials      473      477       +4     

Flag	Coverage Δ
cube-backend	55.13% <100.00%> (+0.02%)	⬆️
cubesql	83.33% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.