Document wildcard tables query support

[findinpath]

Description

Additional context and related issues

https://cloud.google.com/bigquery/docs/querying-wildcard-tables

https://www.elastic.co/guide/en/elasticsearch/reference/current/search-multiple-indices.html

https://opensearch.org/docs/latest/api-reference/multi-search/#metadata-only-options

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`)

[findinpath]

Worth noting from https://cloud.google.com/bigquery/docs/querying-wildcard-tables

Each row in the wildcard table contains a special column, _TABLE_SUFFIX, which contains the value matched by the wildcard character.

Maybe it is worth exposing this hidden column for this specific use case in a follow-up (if this functionality has any traction).
cc @ebyhr

[Ordinant]

Looks right to me.

[mosabua]

At minimum we need to link to other resources that explain what these tables are and what restrictions there are on it. Or better would be if we document ourselves..

Also is this just passing through to the underlying system or is this actually running in Trino .. and what are limitations in terms of WHERE clauses or JOINs or whatever.

For example, I would think that if you have to table .. tbl1 and tbl2 with completely different columns .. doing a wildcard query on them wont work ..

[findinpath]

At minimum we need to link to other resources that explain what these tables are and what restrictions there are on it. Or better would be if we document ourselves..

I decided on linking to other resources option - the data source providers themselves don't specify explicitly the limitations, so I don't see a reason why we should attempt to specify the limitations ourselves.

[mosabua]

Looks good now.

[mosabua]

Thank you @findinpath !

[mosabua]

Related question .. do we need to backfill this feature into some old release notes @findinpath ?