Check Cast Expr Before Adding Equivalences

[berkaysynnada]

Which issue does this PR close?

Closes #9832.

Rationale for this change

Casted columns may lost their ordering. We need check the source and target datatypes to ensure ordering still exists.

What changes are included in this PR?

get_ordering() API of PhysicalExpr's get an optional schema. It only looks up it for cast expressions but I cannot figure out simpler way to get the source datatype of the casted expr. update_ordering() and get_expr_ordering() have been changed for this end.

Are these changes tested?

Yes, added an .slt

Are there any user-facing changes?

[alamb]

Is this PR ready to merge?

[berkaysynnada]

Is this PR ready to merge?

We are thinking on more extendable and user friendly API. Giving schemas as an option can be a misuse, and in the future, we may need to know more information about the children, such as range. When we agree on this, I will re-open.