Add expression evaluation in Presto sidecar

[tdcmeehan]

Description

To support constant folding and consistent semantics between the Presto coordinator (Java) and the Presto C++ worker, it is necessary to use consistent expression evaluation. To support this, a native expression evaluation endpoint, v1/expressions, has been added to the Presto sidecar process, and a plugin has been created which can utilize Velox expression evaluation behind a standard ExpressionOptimizer.

Adds ExpressionOptimizer in Velox to optimize and constant fold TypedExprs via API optimizeExpression(); depends on Velox changes. Optimizes Presto RowExpressions in the Presto native sidecar with following conversion:

RowExpression == (PrestoToVeloxExpr) ==> TypedExpr == (Velox API optimizeExpression()) ==> optimized `TypedExpr` == (RowExpressionConverter) ==> optimized RowExpression

Adds helper class RowExpressionConverter to convert the optimized/constant folded Velox core::TypedExpr to a Presto protocol::RowExpression.

These changes are being reviewed in PR: #22927.

Motivation and Context

Consistency between C++ and Java semantics. Support for using C++ functions during constant folding of expressions in the planner.

Impact

Fix some lingering bugs with C++ clusters.

Test Plan

Tests have been added by extending the TestRowExpressionInterpreter class to also test native expression evaluation in TestNativeExpressionOptimizer.java. The Velox expression fuzzer is extended to ensure the expression optimizations are tested exhaustively. However, this feature is still in Beta, and to support production workloads with complete certainty a fuzzer will be created to surface any remaining bugs with the integration at a later time.

Release Notes

== RELEASE NOTES ==

General Changes
* ... :pr:`12345`
* ... :pr:`12345`

Hive Connector Changes
* ... :pr:`12345`
* ... :pr:`12345`