make type coercion simple and remove the evaluate logic
Is your feature request related to a problem or challenge? Please describe what you are trying to do. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and why for this feature, in addition to the what)
@Dandandan do the optimization in this https://github.com/apache/arrow-datafusion/pull/3444.
But it make the optimizer rule type_coercion complicated, we can add the repeated rule SimplifyExpressions after the type_coercion rule
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
This issue is done in the https://github.com/apache/arrow-datafusion/pull/3396