Add ES|QL full text functions challenges

[carlosdelest]

Adds ES|QL full text functions challenges to existing tracks:

Search use case

Check that full text functions behave correctly for a full text search scenario with enough text data. Sorting by score will be used in all queries.

• Use wikipedia rally track as a base (23M docs), using 1 node / 1 shard / force merge to a single segment.
• Perform queries using ESQL full text functions (MATCH, QSTR, KQL).
• Perform equivalent queries using the query DSL

Observability use case

Perform filtering using full text functions for partial word matches, with no scoring.

• Use elastic/logs rally track - it can provide many shards and it has been already used for ESQL scale testing
• Define full text function queries. Use as a base the text queries done in the different track workflows (searching for exceptions, SQL logs, etc) and add filtering based on time ranges

Closes elastic/elasticsearch#124649

[ioanatia]

looking at the changes in the track.py the ES|QL and query DSL queries should be equivalent (same queries are being used, same queried fields, same source fields being retrieved, same size etc).

[ioanatia]

Is there any impact from this renaming?

[carlosdelest]

The param-source attribute for the query-string-search operation has been changed - no other changes are needed as just the param source is changed and not the actual query name.

[ioanatia]

typo ES@QL

[carlosdelest]

🤦 Done in fe9c146

[ioanatia]

there's a linting CI error that we should fix before merging - there are some extra lines here too that we prob want to remove

[carlosdelest]

Right 🤦 Executed linting in fe9c146

[luigidellaquila]

LGTM