Cluster add/edit error message not handling invalid cert on cluster properly

[whiteradam]

🐛 Bug Report

When adding or editing a cluster within the Data Protect, provider side, configuration, if the cluster you are working with does not have a valid SSL certificate, the error message you get is stating that the FQDN or IP is invalid.

To Reproduce

(Write your steps here:)

1. Have a cluster that has a self signed cert or an expired cert.
2. Make sure your browser has not accepted the risk for the cert problem as this will act as a temp workaround.
3. Try to add said cluster to the VCD plugin.
4. You will get the red error text.

Expected behavior

If the FQDN or IP is not correct the existing error is fine.
BUT if the issue is the SSL certificate is invalid for any reason, the error should state that it is a Certificate issue.

Actual Behavior

Since you only get an error that the FQDN or IP is invalid, you end up checking access to the cluster. In doing so, you likely click past the cert error. By clicking past the cert error, you are temporarily letting your browser bypass the issue. You then go back to the VCD plugin and things progress fine as the error is gone.

BUT the next time you (or anyone else) try to access anything involving the VCD extension, you will get random issues. You would only ever see the cert issue if looking at the dev tools.