### Elasticsearch Version

8.4, 8.5, 8.6

### Installed Plugins

_No response_

### Java Version

_bundled_

### OS Version

Darwin

### Problem Description

The shards availability indicator should always be reporting diagnosis when its status is RED/YELLOW.
However, when an index is on a data node that runs out of disk space it will report RED but no diagnosis.

### Steps to Reproduce

Have multi-node cluster where a data (non-master) node that hosts an index runs out of disk space (the index cannot relocate somewhere else).
Call the Health API and the output will be something along these lines:
```
    "shards_availability": {
      "status": "red",
      "symptom": "This cluster has all shards available.",
      "details": {
        "initializing_primaries": 1,
        "started_replicas": 0,
        "initializing_replicas": 0,
        "unassigned_primaries": 0,
        "started_primaries": 1,
        "creating_primaries": 0,
        "unassigned_replicas": 0,
        "restarting_primaries": 0,
        "restarting_replicas": 0
      },
      "impacts": [
        {
          "id": "elasticsearch:health:shards_availability:impact:primary_unassigned",
          "severity": 1,
          "description": "Cannot add data to 1 index [test_index]. Searches might return incomplete results.",
          "impact_areas": [
            "ingest",
            "search"
          ]
        }
      ] 
    }
``` 

### Logs (if relevant)

_No response_
server/src/main/java/org/elasticsearch/cluster/routing/allocation/ShardsAvailabilityHealthIndicatorService.java
diagnosisDefs.add(ACTION_ENABLE_INDEX_ROUTING_ALLOCATION);
            }
            if (EnableAllocationDecider.Allocation.ALL != clusterLevelAllocation) {
                
                diagnosisDefs.add(ACTION_ENABLE_CLUSTER_ROUTING_ALLOCATION);
            }
        }
        return diagnosisDefs;
    }
    /**
     * Generates a list of diagnoses for common problems that keep a shard from allocating to nodes in a data tier.
     * @param indexMetadata Index metadata for the shard being diagnosed.
     * @param nodeAllocationResults allocation decision results for all nodes in the cluster.
     * @param clusterState the current cluster state.
     * @return A list of diagnoses for the provided unassigned shard
     */
    List<Diagnosis.Definition> checkDataTierRelatedIssues(
        IndexMetadata indexMetadata,
        List<NodeAllocationResult> nodeAllocationResults,
        ClusterState clusterState
    ) {
        List<Diagnosis.Definition> diagnosisDefs = new ArrayList<>();
        if (indexMetadata.getTierPreference().size() > 0) {
            List<NodeAllocationResult> dataTierAllocationResults = nodeAllocationResults.stream()
                .filter(hasDeciderResult(DATA_TIER_ALLOCATION_DECIDER_NAME, Decision.Type.YES))
                .toList();
            if (dataTierAllocationResults.isEmpty()) {
                
                for (String tier : indexMetadata.getTierPreference()) {
                    Optional.ofNullable(ACTION_ENABLE_TIERS_LOOKUP.get(tier)).ifPresent(diagnosisDefs::add);