Support bounds evaluation for temporal data types

[ch-sc]

Which issue does this PR close?

As discussed in 14237 temporal data types should be supported in bounds evaluation.

• Closes Add support for filter selectivity for more expression types #14237.

Rationale for this change

We want to extend the number of expressions that can evaluate bounds to calculate statistics and enable better/more query plan optimisations.

What changes are included in this PR?

• Additional data types are supported: Timestamp, Date, Time, Duration, Interval
• Additional binary operators are supported: NotEq, IsDistinctFrom, IsNotDistinctFrom
• Whether an expression supports bounds evaluation or not is now part of the PhysicalExpr trait and therefore decided by every expression type itself. This will also enable UDFs to implement bounds evaluation.

Are these changes tested?

yes

Are there any user-facing changes?

PhysicalExpr and ScalarUDFImpl change, but both provide default implementations for additional functions.

[berkaysynnada]

Thank you @ch-sc for working on this. When you need a review, I can do that if you ping me.

[ch-sc]

Thanks @berkaysynnada! Yeah I'd like to get a review.

There is still a bug, though, that I don't understand yet. Sometimes the sort operator gets removed as can be seen in the repartition_scan.slt test.

[berkaysynnada]

Sometimes the sort operator gets removed as can be seen in the repartition_scan.slt test.

Seems like you're losing the order requirement somehow