feat: reuse range partitioning for date_trunc aggregation - #26449

…26607)

## Which issue does this PR close?

Closes apache#26605.

## Rationale for this change

`date_bin` returns NULL for unrepresentable timestamp bins. Return an
error instead, matching
[PostgreSQL](https://www.db-fiddle.com/f/h3qSHUSRprbzkX9GBkSuY2/0).

I'm not sure whether DataFusion has a specific policy on returning NULL
versus an error here, but the PostgreSQL precedent seems clear.
Returning NULL because we cannot compute a bin for a non-null timestamp
silently hides a computation failure rather than representing missing
input.

This prepares `date_bin` for avoiding aggregate repartitioning in
[apache#25345](apache#25345), similar to
the `date_trunc` optimization in
[apache#26449](apache#26449). It follows
the error behavior established for `date_trunc` in
[apache#25131](apache#25131).

## What changes are included in this PR?

Make scalar and array timestamp-binning failures return `DATE_BIN
timestamp out of range`. Preserve NULL inputs and successful
wider-arithmetic results.

## What is the testing strategy for this PR?

Unit tests and SQLLogicTests cover overflow errors, scalar/array
consistency, NULL preservation, and representable results across
timestamp precisions.

## Are there any user-facing changes?

Previously NULL-producing timestamp-binning failures now fail the query.

---
This PR was developed with AI assistance. All changes have been
reviewed, and I take full responsibility for this contribution.

…he#26835)

## Which issue does this PR close?

Closes apache#25344.
Closes apache#25345.

This completes the initial single-key work alongside apache#26449. Explicit
origins (apache#26913) and compound range keys (apache#24644) remain follow-ups.

## Rationale for this change

Extend the aggregate-locality optimization from apache#26449 to `date_bin`.
When bins stay within timestamp range partitions, aggregation can skip
the hash shuffle.

## What changes are included in this PR?

Pass literal argument values to the existing admission hook. `INTERVAL
'1 hour'` and `INTERVAL '1 month'` have the same `IntervalMonthDayNano`
type, so types alone cannot distinguish them. Inspecting the literal
value lets `date_bin` require a positive fixed-duration stride without
months, treating each day as 24 hours. `date_trunc` continues to rely
only on argument types.

Initially, admit only two-argument calls over timezone-less nanosecond
timestamps, using that literal stride. Explicit origins and other types
remain excluded.

For example:

```sql
SELECT
    date_bin(INTERVAL '1 hour', event_time) AS hour_bin,
    COUNT(*)
FROM events
GROUP BY hour_bin;
```

For ascending timestamp ranges:

- A split at `01:00` separates hourly bins, so the shuffle can be
skipped.
- A split at `01:30` cuts through the `01:00` bin, so the shuffle
remains.

Every split must pass the existing boundary proof. Evaluation errors
conservatively retain the shuffle. This follows the NULL-to-error fix in
apache#26607.

## What is the testing strategy for this PR?

Unit tests cover admission, hook forwarding, ascending/descending
boundaries, and evaluation errors. SQLLogicTests verify plans and
results for aligned bins, crossing bins, and excluded explicit origins.

## Are there any user-facing changes?

Eligible `date_bin` aggregations can avoid a hash shuffle. Function
results are unchanged.

---

Note: This PR was developed with AI assistance. All changes have been
reviewed, and I take full responsibility for this contribution.

…pache#26716)

## Which issue does this PR close?

- Part of apache#26299

## Rationale for this change

Step 1 from the issue. The per-child closure in
`ensure_distribution_with_stats` works out several flags inline
(`allow_subset_satisfy_partitioning`, `add_roundrobin`,
`needs_repartition`, ...). They depend on each other and can only be
tested through full plan tests right now. This moves them into one place
so they can be unit tested. No behaviour change.

## What changes are included in this PR?

- `ChildPolicyConfig`: the settings that are the same for every child.
- `ChildPolicy::new`: works out the flags for one child. The partial
aggregate check (including the
`partial_aggregate_input_keeps_groups_local` case from apache#26449) is passed
as a closure, so it still only runs when it did before.
- `ChildPolicy::needs_hash_repartition`: the repartition decision from
the hash arm.
- The closure now uses these. The rest of the function is unchanged.

## What is the testing strategy for this PR?

New unit tests in `enforce_distribution.rs` for the flags. The existing
`physical_optimizer` tests and sqllogictests pass without changes.

<!-- screenshot: cargo test -p datafusion-physical-optimizer --lib --
enforce_distribution -->

## Are there any user-facing changes?

No