### Description

The parsing of params in parameterized ES|QL queries appears to be inconsistent with the parsing of non-parameterized ES|QL queries. Some examples on current main:

- ```
  {"query": "row a = 1 | eval x = now() + ?", "params": [{"type":"time_duration", "value":"5 hour"}]}
  ```
  results in the following exception:
  ```
  "type":"parsing_exception","reason":"line 1:23: Cannot cast value [5 hour] of type [KEYWORD] to parameter type [TIME_DURATION]"}],"type":"parsing_exception","reason":"line 1:23: Cannot cast value [5 hour] of type [KEYWORD] to parameter type [TIME_DURATION]"
  ```
- ```
  {"query": "row a = 1 | eval x = now() + ?", "params": ["1 week"]}
  ```
  results in
  ```
  "type":"verification_exception","reason":"Found 1 problem\nline 1:22: [+] has arguments with incompatible types [DATETIME] and [KEYWORD]"
  ```
- ```
  "query": "row a = 1 | eval x = now() + ? week", "params": [1]
  ```
  results in
  ```
  "type":"parsing_exception","reason":"line 1:32: extraneous input 'week' expecting <EOF>"}],"type":"parsing_exception","reason":"line 1:32: extraneous input 'week' expecting <EOF>"
  ```

All the queries work fine if the `?` is manually substituted with the given parameter.

The first two indicate that the parsing of query parameters is not consistent with our normal parsing, type resolution and verification pipeline.

According to @astefan , `version` is affected in a similar way.

x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/parser/ExpressionBuilder.java
import org.elasticsearch.xpack.esql.expression.predicate.operator.arithmetic.Mod;
import org.elasticsearch.xpack.esql.expression.predicate.operator.arithmetic.Mul;
import org.elasticsearch.xpack.esql.expression.predicate.operator.arithmetic.Neg;
import org.elasticsearch.xpack.esql.expression.predicate.operator.arithmetic.Sub;
import org.elasticsearch.xpack.esql.expression.predicate.operator.comparison.In;
import org.elasticsearch.xpack.esql.type.EsqlDataTypes;
import org.elasticsearch.xpack.ql.QlIllegalArgumentException;
import org.elasticsearch.xpack.ql.expression.Alias;
import org.elasticsearch.xpack.ql.expression.Expression;
import org.elasticsearch.xpack.ql.expression.Literal;
import org.elasticsearch.xpack.ql.expression.NamedExpression;
import org.elasticsearch.xpack.ql.expression.UnresolvedAttribute;
import org.elasticsearch.xpack.ql.expression.UnresolvedStar;
import org.elasticsearch.xpack.ql.expression.function.FunctionResolutionStrategy;
import org.elasticsearch.xpack.ql.expression.function.UnresolvedFunction;
import org.elasticsearch.xpack.ql.expression.predicate.logical.And;
import org.elasticsearch.xpack.ql.expression.predicate.logical.Not;
import org.elasticsearch.xpack.ql.expression.predicate.logical.Or;
import org.elasticsearch.xpack.ql.expression.predicate.nulls.IsNotNull;
import org.elasticsearch.xpack.ql.expression.predicate.nulls.IsNull;
import org.elasticsearch.xpack.ql.expression.predicate.regex.RLikePattern;
import org.elasticsearch.xpack.ql.expression.predicate.regex.RegexMatch;
import org.elasticsearch.xpack.ql.expression.predicate.regex.WildcardPattern;
import org.elasticsearch.xpack.ql.tree.Source;
import org.elasticsearch.xpack.ql.type.DataType;
import org.elasticsearch.xpack.ql.type.DataTypeConverter;
import org.elasticsearch.xpack.ql.type.DataTypes;
import org.elasticsearch.xpack.ql.type.DateUtils;
import org.elasticsearch.xpack.ql.util.StringUtils;
import java.math.BigInteger;