ESQL: Add capability to prevent failing mixed tests after Starts/EndsWith Lucene pushdown (#124764)

Continuation of #124641, after different issues arised.

Closes #124693
Closes #124745

The failing BWC tests are checking <8.14 mixed cluster nodes, and SingleValueQuery is sometimes emitting warnings with an empty source.

Author: ivancea

x-pack/plugin/esql/qa/testFixtures/src/main/resources/string.csv-spec

@@ -981,6 +981,7 @@ beta         | Kubernetes cluster
 ;
 
 startsWithLucenePushdownIgnoreMultivalues
+required_capability: starts_with_ends_with_lucene_pushdown
 
 from hosts
 | where starts_with(description, "epsilon")
@@ -1266,6 +1267,7 @@ beta         | Kubernetes cluster
 ;
 
 endsWithLucenePushdownIgnoreMultivalues
+required_capability: starts_with_ends_with_lucene_pushdown
 
 from hosts
 | where ends_with(description, "host")

x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java

@@ -872,6 +872,12 @@ public enum Cap {
          */
         RRF(Build.current().isSnapshot()),
 
+        /**
+         * Lucene query pushdown to StartsWith and EndsWith functions.
+         * This capability was created to avoid receiving wrong warnings from old nodes in mixed clusters
+         */
+        STARTS_WITH_ENDS_WITH_LUCENE_PUSHDOWN,
+
         /**
          * Full text functions can be scored when being part of a disjunction
          */