feat: allow Full joins to reuse range co-partitioning in HashJoinExec

[mattp5657]

Which issue does this PR close?

• ClosesAllow co-partitioned Partitioning::Range inputs for full hash joins #23454.

Rationale for this change

#23184 let compatible range-partitioned inputs satisfy inner partitioned hash joins without repartitioning. Full partitioned equi joins still always went through the conservative hash-repartition path, even when both inputs were already co-partitioned by range on the join key(s). The per-partition unmatched-row tracking in HashJoinExec is already partition-local under PartitionMode::Partitioned (not shared globally like in CollectLeft), so Full-join semantics generalize cleanly to range co-partitioning with no additional bookkeeping required.

What changes are included in this PR?

• Extend HashJoinExec::input_distribution_requirements() to opt JoinType::Full in to allow_range_satisfaction_for_key_partitioning(), alongside the existing JoinType::Inner case. The underlying co_partitioned / compatible_co_partitioning_layout / co_partitioning_satisfied logic in distribution_requirements.rs was already join-type-agnostic, so no changes were needed there.
• Add planner unit tests in enforce_distribution.rs covering both the compatible-layout case (no repartition inserted) and the incompatible-split-points case (repartition still inserted) for JoinType::Full.
• Add a range_partitioned_sparse sqllogictest fixture table with the same partition layout as range_partitioned but only partially overlapping keys, and add sqllogictest coverage in range_partitioning.slt for: a compatible Full join avoiding repartition, an incompatible Full join still repartitioning, and matched/left-only/right-only unmatched rows produced correctly by a co-partitioned Full join.

Are these changes tested?

Yes:

• Two new Rust unit tests in datafusion/core/tests/physical_optimizer/enforce_distribution.rs assert on the physical plan shape (repartition inserted or not) for compatible and incompatible range layouts.
• Three new sqllogictest cases in datafusion/sqllogictest/test_files/range_partitioning.slt exercise the feature end-to-end against real data, including matched rows, left-only unmatched rows, and right-only unmatched rows for a Full outer join.
• Existing enforce_distribution tests, range_partitioning.slt, and proto roundtrip tests all continue to pass.

Are there any user-facing changes?

Yes: EXPLAIN output for Full joins over compatible range-partitioned inputs will no longer show a RepartitionExec, and such queries will avoid the associated hash-shuffle cost at execution time. No public API changes.

[gene-bordegaray]

this looks good, just rebase and ping me for a re-review before I approve 👍

[mattp5657]

@gene-bordegaray This should be ready.

[gene-bordegaray]

this should be good after next addresses 👍

[gene-bordegaray]

lets just have this say "Unsupported"

[gene-bordegaray]

can we add query results

[mattp5657]

@gene-bordegaray Thank you for the comments, this should be ready when you have a chance :)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.67%. Comparing base (4c20fa7) to head (01d6200).

Additional details and impacted files

@@ Coverage Diff @@## main #23583 +/- ##
==========================================
- Coverage 80.67% 80.67% -0.01% 
==========================================
Files 1087 1087 Lines 367541 367566 +25 Branches 367541 367566 +25 ==========================================
+ Hits 296520 296529 +9 - Misses 53365 53376 +11 - Partials 17656 17661 +5 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gene-bordegaray]

thank you 🙇

[gene-bordegaray]

cc: @gabotechs

[gabotechs]

Thanks @mattp5657 and @gene-bordegaray!