**Current behaviour**
The disk indicator reports the following when a data node is yellow or red but has no indices.
- Symptom: 
> 1 node with roles: [data] is out of disk or running low on disk space.
- Impact: None
- Diagnosis:
> 0 indices reside on nodes that have run or are likely to run out of space, this can temporarily disable writing on these indices. 
> Enable autoscaling (if applicable), add disk capacity or free up disk space to resolve this. If you have already taken action please wait for the rebalancing to complete.

**Expected behaviour**
The disk indicator reports the following when a data node is yellow or red but has no indices.
- Symptom:
> 1 node with roles: [data] is out of disk or running low on disk space.
- Impact:
> 1 node with roles: [data] has run out or is likely to run out of disk space, this node cannot be used by the cluster to store data. `AREA: DEPLOYMENT_MANAGEMENT`
- Diagnosis:
> Disk is almost full.
> Enable autoscaling (if applicable), add disk capacity or free up disk space to resolve this. If you have already taken action please wait for the rebalancing to complete.

As an area of impact I added `DEPLOYMENT_MANAGEMENT` considering that this is not a healthy deployment if one node is not usable. I am trying to avoid listing `INGEST` since for now we can still ingest data. Any thoughts?

See: #90305
server/src/main/java/org/elasticsearch/health/node/DiskHealthIndicatorService.java
*/
    private void logNodesMissingHealthInfo(Map<String, DiskHealthInfo> diskHealthInfoMap, ClusterState clusterState) {
        if (logger.isDebugEnabled()) {
            String nodesMissingHealthInfo = getSortedUniqueValuesString(
                clusterState.getNodes(),
                node -> diskHealthInfoMap.containsKey(node.getId()) == false,
                HealthIndicatorDisplayValues::getNodeName
            );
            if (nodesMissingHealthInfo.isBlank() == false) {
                logger.debug("The following nodes are in the cluster state but not reporting health data: [{}]", nodesMissingHealthInfo);
            }
        }
    }
    /**
     * The disk health analyzer takes into consideration the blocked indices and the health status of the all the nodes and calculates
     * the different aspects of the disk indicator such as the overall status, the symptom, the impacts and the diagnoses.
     */
    static class DiskHealthAnalyzer {
        public static final String INDICES_WITH_READONLY_BLOCK = "indices_with_readonly_block";
        public static final String NODES_WITH_ENOUGH_DISK_SPACE = "nodes_with_enough_disk_space";
        public static final String NODES_OVER_FLOOD_STAGE_WATERMARK = "nodes_over_flood_stage_watermark";
        public static final String NODES_OVER_HIGH_WATERMARK = "nodes_over_high_watermark";
        public static final String NODES_WITH_UNKNOWN_DISK_STATUS = "nodes_with_unknown_disk_status";
        private final ClusterState clusterState;
        private final Set<String> blockedIndices;
        private final List<DiscoveryNode> dataNodes = new ArrayList<>();
        
        private final Map<HealthStatus, List<DiscoveryNode>> masterNodes = new HashMap<>();
        
        private final Map<HealthStatus, List<DiscoveryNode>> otherNodes = new HashMap<>();