[TRACKING] DataFusion issues raised by Ballista

Tracking tasks with DataFusion issues which ballista benefits from:

## DataFusion <46

- https://github.com/apache/datafusion/issues/13616
- https://github.com/apache/datafusion/issues/14003
- https://github.com/apache/datafusion/issues/14654

## DataFusion 46

- https://github.com/apache/datafusion/issues/14679

## DataFusion 47

- https://github.com/apache/datafusion/pull/15311
- https://github.com/apache/datafusion/issues/15087

## DataFusion 48

- https://github.com/apache/datafusion/issues/15718

## DataFusion 50

- https://github.com/apache/datafusion/issues/17292
- https://github.com/apache/datafusion/issues/17649

## DataFusion 51

- https://github.com/apache/datafusion/issues/17596

## DataFusion 52

- https://github.com/apache/datafusion/issues/17297

## DataFusion 53

- https://github.com/apache/datafusion/issues/20280
- https://github.com/apache/datafusion/pull/19757

## DataFusion 54

- https://github.com/apache/datafusion/issues/16944
- https://github.com/apache/datafusion/pull/21994

## DataFusion 55

- https://github.com/apache/datafusion/pull/22241
- https://github.com/apache/datafusion/pull/22522
- https://github.com/apache/datafusion/pull/22523

## Open Issues

Raised issues which have no fix version yet

- https://github.com/apache/datafusion/issues/16945

It's getting harder and harder to track what is going to get supported in which version

Start by reviewing the linked DataFusion issues and pull requests, grouped by the listed DataFusion versions. Determine each item's current status and target support version, then update the tracking information so every task has an unambiguous disposition and the supported-version picture is clear.

Written by the indexing model from the issue text.