Ozone: OzoneRestClientException swallows exceptions which makes client hard to debug failures

There are multiple try-catch places swallow exceptions when transforming some other exception to OzoneRestClientException. As a result, when client runs into such code paths, they lose track of what was going on which makes the debug extremely difficult. See below example

bin/hdfs oz -listBucket  http://15oz1.fyre.ibm.com:9864/vol-0-84022 -user wwei
Command Failed : {"httpCode":0,"shortMessage":"Read timed out","resource":null,"message":"Read timed out","requestID":null,"hostName":null}

the returned message doesn't help much on debugging where and how it reads timed out.