Reduce ClickHouse lookup memory use and scan time

[Telesphoreo]

Summary

ClickHouse compatibility views converted binary strings into Array(Int8) values one byte at a time. A rollback lookup could allocate several gigabytes before it returned any rows. The views also wrapped location columns in if expressions, which caused spatial lookups to scan more data than needed.

This PR upgrades the ClickHouse JDBC driver to 0.10.0 and enables its binary string support. CoreProtect can now read binary columns as raw bytes without building per-byte arrays in ClickHouse.

Location inspectors now read event_data FINAL directly. They filter the stored family, wid, x, and z columns, which match the start of the table sorting key. Compatibility views also project stored location columns without if wrappers.

Union queries now use numeric tbl values. This prevents ResultSet.getInt("tbl") from failing with the newer JDBC driver.

Testing

• Built with mvn -DskipTests package.
• Checked block inspection on a live ClickHouse database.
• Checked a one-day rollback lookup with a 50-block radius on the same database.

Fixes #965