DataFusion's casting semantics incompatibilities are causing runtime errors

[AdamGS]

Due to DataFusion's improved projection pushdown, we now push some cast expressions into our scans, in ways that are incompatible with Vortex's cast semantics.

Examples

1. Cast error when casting integer type to string in select statement with datafusion-vortex #6211
2. Panic when handle schema evolution in vortex file #6264

[gatesn]

@AdamGS do we get to yay/nay the projection push-down in the same way as filter push-down? If so then we probably need some way of saying whether a particular cast is supported.

If not... I'm not sure how we can guarantee forever more that we support a super-set of DataFusion casts.

[AdamGS]

That's basically the discussion I had with @robert3005.
Currently DF doesn't let you explicitly say what projection expressions you support or not, but we have our own thing that basically splits the projection into parts we supports and parts we don't.

I think formalizing our casting semantics and exposing the expectations programmatically would be very useful, and the splitting logic would be able to take advantage of that (it already does for decimals, but there are many more cases obviously).