### Elasticsearch Version

8.x

### Installed Plugins

_No response_

### Java Version

_bundled_

### OS Version

Darwin

### Problem Description

Searching a filtered and a non-filtered data stream alias that both point to the same datastream currently filter the result set 
(relevant [code](https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/cluster/metadata/IndexNameExpressionResolver.java#L714)  )

The desired behaviour is to **not** consider the filter in this case and return the (wider) un-filtered result.

(the desired behaviour for data stream aliases currently exists for indices aliases - relevant code that abandons applying the filter for _index aliases_ is [here](https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/cluster/metadata/IndexNameExpressionResolver.java#L743) )

### Steps to Reproduce

```
PUT _index_template/datastream-template
{
  "index_patterns": [
    "my-datastream"
  ],
  "data_stream": {
  }, 
  "template": {
    "aliases": {
      "first_alias": {
        "filter": {
          "term": {
            "message": "first"
          }
        }
      },
      "second_alias": {}
    }
  },
  "composed_of": []
}



POST my-datastream/_doc
{
  "message":"first",
  "@timestamp":"2023-05-02T08:02:40.420Z"
}


POST my-datastream/_doc
{
  "message":"second",
  "@timestamp":"2023-05-02T08:02:40.420Z"
}

GET first_alias,second_alias/_search
```

The `GET first_alias,second_alias/_search` call only returns one hit, while it should return 2.

### Logs (if relevant)

_No response_
server/src/test/java/org/elasticsearch/indices/IndicesServiceTests.java
* a new index A with UUID 2, then shutdown, when the node comes back online, it will look at the
     * tombstones for deletions, and it should proceed with trying to delete A with UUID 1 and not
     * throw any errors that the index still exists in the cluster state.  This is a case of ensuring
     * that tombstones that have the same name as current valid indices don't cause confusion by
     * trying to delete an index that exists.
     * See https://github.com/elastic/elasticsearch/issues/18054
     */
    public void testIndexAndTombstoneWithSameNameOnStartup() throws Exception {
        final String indexName = "test";
        final Index index = new Index(indexName, UUIDs.randomBase64UUID());
        final IndicesService indicesService = getIndicesService();
        final Settings idxSettings = Settings.builder()
            .put(IndexMetadata.SETTING_VERSION_CREATED, Version.CURRENT)
            .put(IndexMetadata.SETTING_INDEX_UUID, index.getUUID())
            .build();
        final IndexMetadata indexMetadata = new IndexMetadata.Builder(index.getName()).settings(idxSettings)
            .numberOfShards(1)
            .numberOfReplicas(0)
            .build();
        final Index tombstonedIndex = new Index(indexName, UUIDs.randomBase64UUID());
        final IndexGraveyard graveyard = IndexGraveyard.builder().addTombstone(tombstonedIndex).build();
        final Metadata metadata = Metadata.builder().put(indexMetadata, true).indexGraveyard(graveyard).build();
        final ClusterState clusterState = new ClusterState.Builder(new ClusterName("testCluster")).metadata(metadata).build();
        
        indicesService.verifyIndexIsDeleted(tombstonedIndex, clusterState);
    }
    /**
     * Tests that teh {@link MapperService} created by {@link IndicesService#createIndexMapperServiceForValidation(IndexMetadata)} contains
     * custom types and similarities registered by plugins
     */