[BUG] Index patterns in nested collection queries

What is the bug?

Using wildcards in index name works for simple queries only. Self-joined queries fail. More details in index-patterns-for-querying-nested-collection discussion:

How can one reproduce the bug?
Steps to reproduce the behavior:

1. Use sample data from:
   https://opensearch.org/docs/latest/search-plugins/sql/sql/partiql/

Map array of object as nested type.

2. Query nested collection using index pattern employees* :

SELECT e.name AS employeeName,
       p.name AS projectName
FROM employees* AS e,
       e.projects AS p
WHERE p.name LIKE '%security%'

Result:

{
  "error": {
    "reason": "There was internal problem at backend",
    "details": "Index type [employees*] does not exist",
    "type": "IllegalArgumentException"
  },
  "status": 500
}

What is the expected behavior?
Search all indexes matching a given pattern

What is your host/environment?
2.6.0

Start with the SQL/PartiQL nested-collection example and reproduce the query against the sample data using the employees* index pattern. Trace how index patterns are handled for the self-joined nested query. Done means the query searches all matching indexes instead of returning the "Index type [employees*] does not exist" error.