### 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/test/java/org/elasticsearch/cluster/metadata/IndexNameExpressionResolverTests.java
assertThat(IndexNameExpressionResolver.isExplicitAllPattern(Collections.<String>emptyList()), equalTo(false));
    }
    public void testIsExplicitAllIndicesExplicitAll() throws Exception {
        assertThat(IndexNameExpressionResolver.isExplicitAllPattern(Arrays.asList("_all")), equalTo(true));
    }
    public void testIsExplicitAllIndicesExplicitAllPlusOther() throws Exception {
        assertThat(IndexNameExpressionResolver.isExplicitAllPattern(Arrays.asList("_all", "other")), equalTo(false));
    }
    public void testIsExplicitAllIndicesNormalIndexes() throws Exception {
        assertThat(IndexNameExpressionResolver.isExplicitAllPattern(Arrays.asList("index1", "index2", "index3")), equalTo(false));
    }
    public void testIsExplicitAllIndicesWildcard() throws Exception {
        assertThat(IndexNameExpressionResolver.isExplicitAllPattern(Arrays.asList("*")), equalTo(false));
    }
    public void testIndexOptionsFailClosedIndicesAndAliases() {
        Metadata.Builder mdBuilder = Metadata.builder()
            .put(
                indexBuilder("foo1-closed").state(IndexMetadata.State.CLOSE)
                    .putAlias(AliasMetadata.builder("foobar1-closed"))
                    .putAlias(AliasMetadata.builder("foobar2-closed"))
            )
            .put(indexBuilder("foo2-closed").state(IndexMetadata.State.CLOSE).putAlias(AliasMetadata.builder("foobar2-closed")))
            .put(indexBuilder("foo3").putAlias(AliasMetadata.builder("foobar2-closed")));
        ClusterState state = ClusterState.builder(new ClusterName("_name")).metadata(mdBuilder).build();
        IndexNameExpressionResolver.Context contextICE = new IndexNameExpressionResolver.Context(
            state,
            IndicesOptions.strictExpandOpenAndForbidClosed(),
            SystemIndexAccessLevel.NONE
        );
        expectThrows(IndexClosedException.class, () -> indexNameExpressionResolver.concreteIndexNames(contextICE, "foo1-closed"));