fix date_trunc overflows converting extreme non-ns timestamps to nanoseconds (#22262)

## Which issue does this PR close?
- Closes #22209

## Rationale for this change
`date_trunc` can panic during planning and constant folding when it
receives extreme non-nanosecond timestamps. The overflow happens while
converting values to nanoseconds, so a valid SQL query can crash the
planner instead of returning a proper error. This change makes that path
fail gracefully with a planning error.

## What changes are included in this PR?
- Adds overflow checks to the timestamp scale conversion used by
`date_trunc`.
- Converts the panic into a normal out-of-range planning error.
- Adds regression coverage for extreme `Timestamp(Second)`,
`Timestamp(Millisecond)`, and `Timestamp(Microsecond)` inputs.
- Adds a SQL-level regression test for the `arrow_cast(...)` plus
`date_trunc(...)` repro.

## Are these changes tested?
- Yes. I added regression tests and verified the repro now returns an
error instead of panicking.

## Are there any user-facing changes?
- Yes. Out-of-range timestamp inputs now produce a planning error rather
than aborting the query with a panic.

Author: xiedeyantu

datafusion/functions/src/datetime/date_trunc.rs

@@ -718,7 +718,13 @@ fn general_date_trunc(
     };
 
     // convert to nanoseconds
-    let nano = date_trunc_coarse(granularity, scale * value, tz)?;
+    let nano = date_trunc_coarse(
+        granularity,
+        value
+            .checked_mul(scale)
+            .ok_or_else(|| exec_datafusion_err!("Timestamp {value} out of range"))?,
+        tz,
+    )?;
 
     let result = match tu {
         Second => match granularity {

datafusion/sqllogictest/test_files/datetime/timestamps.slt

@@ -2428,6 +2428,12 @@ SELECT arrow_typeof(date_trunc('hour', TIME '14:30:45'));
 ----
 Time64(ns)
 
+query error DataFusion error: Execution error: Timestamp 9223372036854775807 out of range
+SELECT date_trunc(
+  'hour',
+  arrow_cast(9223372036854775807, 'Timestamp(Second, None)')
+);
+
 # Error for granularities not valid for Time types
 query error date_trunc does not support 'day' granularity for Time types
 SELECT date_trunc('day', TIME '14:30:45');