fix(datafusion): preserve boolean expression literal types

[lance-gatefixer]

Summary

• resolve typed right-hand expressions in their own column context
• retain column-type coercion for literal-only same-type expressions, including shifts and string concatenation
• add planning and execution coverage for Boolean and constant-expression comparisons

Root cause

The filter resolver recursively coerced every literal inside any right-hand binary expression to the type of the outer left column. When the outer column was Boolean, literals belonging to nested numeric comparisons were incorrectly converted to Boolean before DataFusion planned the expression.

Validation

• cargo fmt --all
• cargo test -p lance-datafusion (188 tests and doctests passed)
• cargo clippy --all --tests --benches -- -D warnings

Fixes #9319

[lance-gatekeeper]

✅ Gate recommendation: approve.

The prior non-blocking coercion risk is fixed in e6c385771: supported constant shifts and string concatenation now retain the column type, with execution regression tests covering both. The original Boolean-expression fix remains intact and no material residual risk remains.