feat!: upgrade DataFusion fork to 55.1.0

[discord9]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

Follow-up to #8555 (DataFusion 55 upgrade). Built on the statistics migration in #9175.

What's changed and what's your intention?

Moves the GreptimeDB DataFusion fork pin from official 55.0.0 to 55.1.0.

DataFusion 55.1.0 is a patch release cut from branch-55 containing eleven cherry-picked fixes, none of which absorbs any GreptimeDB fork patch. The upgrade exists to pick up upstream fixes we would otherwise have to backport by hand — most notably the cast/projection metadata propagation repairs (#23169, #24670), which are in the same area as the field-metadata issues we patched locally during #8555.

55.1.0 contents (11 commits over 55.0.0): schema-adaptation struct field filters (#24125), nested-nullability aggregation batch adaptation (#24394), cast metadata alignment (#23169), projection metadata preservation (#24670), UnnestExec batch_size (#24384), RightMark join ordering panic (#24718), empty-struct ScalarValue (#24582), two FFI codec fixes, minor dependency updates, version bump.

Fork status: all twenty GreptimeDB fork patches are retained. Verified via GitHub compare/branch inspection that none of their corresponding upstream PRs is contained in 55.1.0:

• Still open upstream: #23800 (global multi-partition fetch), #22906 (safe cast preimages), #25065 (distribution enforcement).
• Merged to main but not in branch-55: #24686, #24846, #24817, #24248/#24380/#24763.
• Fork-only patches (Substrait duplicate roots, timestamp widening, dictionary grouping/serialization, OneOf error classification, EXPLAIN pgjson ordering, etc.) have no upstream counterpart.

Rebase verification: the twenty patches were rebased onto 55.1.0 (7d3835c71f30cbd3c3ae4041732267f1f453097a) with zero textual conflicts. The two fork patches touching related areas were checked for semantic overlap against the 55.1.0 metadata fixes and touch disjoint files (logical optimizer optimize_projections vs physical-plan projection.rs; expr-common/casts.rs simplifier vs physical-expr/expressions/cast.rs).

New fork pin: discord9/datafusion branch greptimedb-55.1.0, commit 2aa87d52cdce7006af492330064738f33ed294c1 (= official 55.1.0 + 20 patches). All 14 datafusion* workspace version constraints move =55.0.0 → =55.1.0; all 15 [patch.crates-io] revs and 35 lockfile source blocks move to the new pin.

All CI checks pass (41/41), including the five sqlness suites, all fuzz targets (Remote-WAL migration and logical pruning included), Export/Import V2 E2E, Clippy, unused-dependency check, and the Windows/riscv64 builds. Coverage and the recent-releases compatibility job skip on this PR as usual.

Verification:

• cargo check -p datafusion-physical-expr -p datafusion-optimizer -p datafusion-physical-plan -p datafusion-expr-common on the rebased fork
• cargo check -p table -p query (GreptimeDB)
• cargo clippy -p table -p query --tests -- -D warnings
• cargo nextest run -p table (89/89, including the fix: preserve count correctness after repartition #9154 test_count_statistics_require_exact_source_rows gate)

PR Checklist

Please convert it to a draft if some of the following conditions are not met.

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.
• API changes are backward compatible.
• Schema or data changes are backward compatible.

[github-actions]

Warning

@discord9 has 12 open non-draft pull requests in this repository, over the limit of 5.

Review is the scarcest resource here. Please land or close some of these before
pushing this one forward.

• PR 8918: fix(client): yield Flight batches and affected rows without waiting for next message
• PR 8976: refactor(flow): execute streaming flows with DataFusion
• PR 9030: fix(client): complete transport lane isolation
• PR 9035: feat(flow): support incremental aggregate state merging and execution extensions
• PR 9071: fix(query): preserve global limits with DataFusion optimizer fixes
• PR 9077: feat(mito2): support lazy ALTER of float SST encoding
• PR 9108: perf(promql): avoid concatenating constant series tags
• PR 9167: perf(servers): coalesce ready Flight record batches
• PR 9171: feat(flow): expose extension-owned batching execution hooks
• PR 9175: refactor: migrate partition_statistics to statistics_from_inputs
• ...and 1 more

View your open pull requests

This check is advisory for now and blocks nothing.

[sunng87]

Is this still a breaking change?