[ES|QL] Make EvaluatorMapper.fold() throw VerificationException for folding time errors Option #2

[fang-xing-esql]

This is an alternative approach to wrap constant folding errors into VerificationExceptions, instead of returning warnings + nulls.

Resolves: #112672
Resolves: #99758
Resolves: #108519

The first approach is here

Previously, the warnings/exceptions created by ExpressionEvaluator are stored in thread_context, and they are not returned to planner after constant folding, so they are not visible to planner. This PR adds a method evalFoldable that throw Exceptions for errors happen during the evaluation of foldable expressions in ExpressionEvaluator, and it is called by EvaluatorMapper.fold() during LogicalPlanOptimizer. evalFoldable does not create warnings and add them into thread_context, it throws the Exception when there is error happens directly, later on these Exceptions are wrapped into VerificationExceptions by EvaluatorMapper.fold(), ConstantFolding and PropagateEvalFoldables.

Conversion functions are not covered by this PR yet. There are some examples in the CsvTests that are referenced by docs.

[elasticsearchmachine]

Hi @fang-xing-esql, I've created a changelog YAML for you.

[astefan]

Instead of calling this method in ConstantFolding and PropagateEvalFoldables have you thought about calling it in Literal.of() when the fold() method is called on the Literal constructor?

[astefan]

Foldables is also calling fold on a foldable expression... Off the top of my head, I don't remember why we have that. It seems there are some special cases for in and some geo-related logic that need it.