Add a new optional field called cluster_reason. the format follows UpperCamelCase naming convention. It should support customizing. One typical use case is that if the cluster is failed, we may need to know the specific reason (DNSResolutionFailure/APIServerFailure etc)

Acceptance criteria

• Add `cluster_reason` string field as optional field to cluster details 
• Update the java/go client