In some contexts is unclear why an autoscaling policy decides to request
more resources, i.e. if there's an unassigned shard that remains unassigned
even after adding more resources. It would be help to have more information
around the decisions taken by the deciders so it is easier to understand and
track them.
x-pack/plugin/autoscaling/src/test/java/org/elasticsearch/xpack/autoscaling/storage/ReactiveStorageDeciderDecisionTests.java
}
        @Override
        public ClusterInfo info() {
            return info;
        }
        @Override
        public SnapshotShardSizeInfo snapshotShardSizeInfo() {
            return null;
        }
        @Override
        public void ensureNotCancelled() {
        }
    }
    private static ClusterInfo createClusterInfo(ClusterState state) {
        
        
        Map<String, DiskUsage> diskUsages = state.nodes()
            .stream()
            .collect(Collectors.toMap(DiscoveryNode::getId, node -> new DiskUsage(node.getId(), null, "the_path", 1000, 1000)));
        ImmutableOpenMap<String, DiskUsage> immutableDiskUsages = ImmutableOpenMap.<String, DiskUsage>builder()
            .putAllFromMap(diskUsages)
            .build();
        return new ClusterInfo() {
            @Override
            public Map<String, DiskUsage> getNodeLeastAvailableDiskUsages() {
                return immutableDiskUsages;
            }
            @Override
            public Map<String, DiskUsage> getNodeMostAvailableDiskUsages() {
                return immutableDiskUsages;