feat(datafusion): add push down temporal literals

[liujiwen-up]

Purpose

DataFusion filter pushdown currently cannot translate temporal literal ScalarValues into Paimon Datums, so predicates on Paimon TIME, TIMESTAMP, and TIMESTAMP WITH LOCAL TIME ZONE columns fall open unnecessarily.

Changes

• Translate ScalarValue::Time32Millisecond into Datum::Time for Paimon Time fields.
• Translate timezone-free TimestampSecond / TimestampMillisecond / TimestampMicrosecond / TimestampNanosecond into Datum::Timestamp.
• Translate timezone-bearing timestamp scalar values into Datum::LocalZonedTimestamp.
• Use div_euclid / rem_euclid for sub-millisecond timestamp parts so negative timestamps before 1970 split correctly.
• Keep timezone semantic mismatches unsupported so DataFusion residual filters continue to preserve correctness.

Tests

• cargo test -p paimon-datafusion filter_pushdown
• cargo test -p paimon-datafusion --test read_tables test_temporal_filter_pushdown_via_datafusion_scan -- --nocapture
• cargo test -p paimon-datafusion was also run locally; all new filter_pushdown tests passed, but the full package run hit existing fixture-dependent failures for missing default.partitioned_log_table / default.multi_partitioned_log_table in table::tests::*scan* tests.

[QuakeWang]

This residual predicate is true for the row matched by the temporal predicate, so the result would stay the same even if the residual filter were dropped. Could we make the residual condition actually filter out a temporal match, or assert the plan still contains a residual FilterExec?

[JingsongLi]

+1

[QuakeWang]

LGTM