CONTAP-113520: Cloud KMS "reachable" status displays true while "message" and "code" indicate an error

Issue

When checking Cloud KMS (Key Management Service) reachability via the ONTAP REST API, the global reachability status incorrectly shows as reachable but the message field indicates that a subset of nodes are unable to reach the service and the code field has a non-zero value.
This could happen when checking the reachability immediately after enabling a Cloud KMS feature (ex. AKV KMS, GCP KMS, AWS KMS).
Example REST output with issue:
"azure_reachability": {
"reachable": true,
"message": "Azure Key Vault unreachable from the following nodes: Node: OntapNode0. Reason: Azure Key Vault (AKV) operation \"GET\" failed.\nCryptsoft error: IO\nCryptsoft status: SUCCESS\nCryptsoft reason: SUCCESS\nCryptsoft message: \nHTTP response code: \nHTTP payload: \n\nUnable to communicate with the AKV instance.\nIssue (privilege: diag) \"security key-manager external <azure|aws|gcp|ikp> invoke\" for more information. ",
"code": "65537549"
}
As an example, if all nodes are actually able to reach an AKV instance, the REST output will look like the following:
"azure_reachability": {
"reachable": true,
"message": "",
"code": "0"
}