Showcase support for reading wildcard tables in Elasticsearch & OpenSearch

[findinpath]

Description

This contribution documents in the code that the trino-elasticsearch connector supports
querying wildcard tables through the trino-elasticsearch connector.

SELECT * from elasticsearch."default"."heartbeat-*"

Additional context and related issues

Test was inspired from #12428 trino-bigquery effort.

Querying wildcard tables is a feature supported by ES to allow searching multiple indexes at the same time (a common pattern where people shard their data sets across indexes for retention, etc): https://www.elastic.co/guide/en/elasticsearch/reference/current/search-multiple-indices.html

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

[mosabua]

If this is supported and syntax is approved by @martint we should definitely document in this connector docs. Probably also in BigQuery.. and maybe OpenSearch connector as well?

Although arguably its kinda weird that we support that syntax ..

[ebyhr]

Can we add another test with different index definition? e.g. long vs text, 2 columns vs 1 column

[findinpath]

I tried both scenarios locally and the results are unpredictable - it basically depends which index is used to retrieve the table schema.
This syntax is thought specifically for tables with the same schema.

[mayankvadariya]

Its worth adding a comment that querying wild card tables work only for the same schema tables.

[findinpath]

No. I see this test more of a "demo" and nothing else.
Bending the functionality as Yuya suggested or speaking about the limitations, is just asking for eventual changes in the future if the functionality slightly changes on the underlying data source.

[findinpath]

we should definitely document in this connector docs.

@mosabua see #25108