Avoid comparison coercion logic comparison_binary_numeric_coercion in non-comparison coercion logic coerced_from #10241
Description
Is your feature request related to a problem or challenge?
I think the logic between these two logic is easily misuse, before someone come out a nice way to handle coercion logic in one. I think we should keep them separate and refrain from mixing their use
#10221 (comment)
Describe the solution you'd like
Remove comparison_binary_numeric_coercion from coerced_from but avoid breaking existing logic.
datafusion/datafusion/expr/src/type_coercion/functions.rs
Lines 456 to 464 in bab39f7
Describe alternatives you've considered
No response
Additional context
No response