### Elasticsearch Version

8.6.0

### Installed Plugins

_No response_

### Java Version

_bundled_

### OS Version

Docker

### Problem Description

When testing datemath with complex date strings, I found that some worked and some didn't. I narrowed it down to the existence of the `|` pipe character in the string.

@dakrone seems to think this may be due to how the `IndexNameExpressionResolver` works differently for security-enabled vs. non-security-enabled clusters.

### Steps to Reproduce

## Security Disabled Cluster
```
curl -XGET 'http://localhost:9200/%3Cdatemath-%7B2001-01-01-13%7C%7C%2B1h%2Fh%7Byyyy-MM-dd-HH%7C-07%3A00%7D%7D%3E'
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Cross-cluster calls are not supported in this context but remote indices were requested: [<datemath-{2001-01-01-13||+1h/h{yyyy-MM-dd-HH|-07:00}}>]"}],"type":"illegal_argument_exception","reason":"Cross-cluster calls are not supported in this context but remote indices were requested: [<datemath-{2001-01-01-13||+1h/h{yyyy-MM-dd-HH|-07:00}}>]"},"status":400}%
```

## Security Enabled Cluster

```
curl -XGET -u sample -p 'https://secure.cluster.io/%3Cdatemath-%7B2001-01-01-13%7C%7C%2B1h%2Fh%7Byyyy-MM-dd-HH%7C-07%3A00%7D%7D%3E'
Enter host password for user 'sample':
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [datemath-2001-01-01-14]","index_uuid":"_na_","index":"datemath-2001-01-01-14"}],"type":"index_not_found_exception","reason":"no such index [datemath-2001-01-01-14]","index_uuid":"_na_","index":"datemath-2001-01-01-14"},"status":404}%
```

### Logs (if relevant)

_No response_
server/src/main/java/org/elasticsearch/cluster/metadata/IndexNameExpressionResolver.java
if (expressions == null || expressions.length == 0 || expressions.length == 1 && Metadata.ALL.equals(expressions[0])) {
                return List.of();
            } else {
                return ExplicitResourceNameFilter.filterUnavailable(
                    context,
                    DateMathExpressionResolver.resolve(context, List.of(expressions))
                );
            }
        } else {
            if (expressions == null
                || expressions.length == 0
                || expressions.length == 1 && (Metadata.ALL.equals(expressions[0]) || Regex.isMatchAllPattern(expressions[0]))) {
                return WildcardExpressionResolver.resolveAll(context);
            } else {
                return WildcardExpressionResolver.resolve(
                    context,
                    ExplicitResourceNameFilter.filterUnavailable(context, DateMathExpressionResolver.resolve(context, List.of(expressions)))
                );
            }
        }
    }
    /**
     * Translates the provided index expression into actual concrete indices, properly deduplicated.
     *
     * @param state             the cluster state containing all the data to resolve to expressions to concrete indices
     * @param options           defines how the aliases or indices need to be resolved to concrete indices
     * @param indexExpressions  expressions that can be resolved to alias or index names.
     * @return the resolved concrete indices based on the cluster state, indices options and index expressions
     * @throws IndexNotFoundException if one of the index expressions is pointing to a missing index or alias and the
     * provided indices options in the context don't allow such a case, or if the final result of the indices resolution