HDDS-13667. [DiskBalancer] Improve DiskBalancer CLI message for failed commands

[Gargi-jais11]

What changes were proposed in this pull request?

Currently DiskBalancer start, stop and update command is send only to IN_SERVICE_HEALTHY DN but user has no info about this so improve cli output message to show as below:

bash-5.1$ ozone admin datanode diskbalancer start -t 0.0001 -a
Starting DiskBalancer on datanode(s) which are IN_SERVICE and HEALTHY. 

When start, stop and update command is sent to a specific DN which is not IN_SERVICE_HEALTHY, command should be rejected same as when sent to all DN.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-13667

How was this patch tested?

Updated existing Integration Test TestDiskBalancerDuringDecommissionAndMaintenance .
Also tested manually on docker-cluster:

bash-5.1$ ozone admin datanode decommission -id scmservice ozone-ha-datanode-5
Started decommissioning datanode(s):
ozone-ha-datanode-5

bash-5.1$ ozone admin datanode diskbalancer status
Status result:
Datanode                            Status          Threshold(%)    BandwidthInMB   Threads      SuccessMove  FailureMove  BytesMoved(MB)  EstBytesToMove(MB) EstTimeLeft(min)
ozone-ha-datanode-3.ozone-ha_default STOPPED         10.0000         200             5            0            0            0               0               0              
ozone-ha-datanode-2.ozone-ha_default STOPPED         10.0000         200             5            0            0            0               0               0              
ozone-ha-datanode-4.ozone-ha_default STOPPED         10.0000         200             5            0            0            0               0               0              
ozone-ha-datanode-1.ozone-ha_default STOPPED         10.0000         200             5            0            0            0               0               0              

Note: Estimated time left is calculated based on the estimated bytes to move and the configured disk bandwidth.

bash-5.1$ ozone admin datanode diskbalancer start -b 200 -d ozone-ha-datanode-5
Error: ozone-ha-datanode-5.ozone-ha_default: Datanode is not in optimal state for disk balancing. NodeStatus: DECOMMISSIONING(no expiry)-HEALTHY
Some nodes could not start DiskBalancer.

bash-5.1$ ozone admin datanode decommission -id scmservice ozone-ha-datanode-3 
Started decommissioning datanode(s):
ozone-ha-datanode-3

bash-5.1$ ozone admin datanode decommission -id scmservice ozone-ha-datanode-4 
Started decommissioning datanode(s):
ozone-ha-datanode-4

bash-5.1$ ozone admin datanode diskbalancer start -t 0.002 -a
Starting DiskBalancer on datanode(s) which are IN_SERVICE and HEALTHY.

[sarvekshayr]

Thanks for the patch @Gargi-jais11.

[sarvekshayr]

Thanks for updating the patch. Please change the log message from the first output in the PR description.

[sumitagrawl]

@Gargi-jais11 Given minor comment

[sumitagrawl]

LGTM

[ChenSammi]

Thanks @Gargi-jais11 for the contribution, and @sumitagrawl for the review.