knife ssl check mismatched cert error message is not helpful

I burned a ton of time after hitting this one. It seems like a common getting started error with Chef that we should really handle better. If you spin up a node in EC2 it ends up with the cert being signed by the internal hostname and you can't use that self signed cert with knife. The solution it to update the API URL in the server config and reconfigure, but good luck finding anything online to tell you that. We should expand this error message to point to some sort of help documentation otherwise users are going to just drop off here after they can't get the server and knife to talk w/o turning off SSL verification.

Connecting to host 34.213.52.123:443
ERROR: The SSL cert is signed by a trusted authority but is not valid for the given hostname
ERROR: You are attempting to connect to:   '34.213.52.1233'
ERROR: The server's certificate belongs to 'ip-172-31-25-123.us-west-2.compute.internal'```

Start by locating the implementation of knife ssl check and the code that emits the hostname/certificate mismatch errors. Review the related help documentation, then update the error guidance so users can find the server configuration and reconfiguration steps; done means the reported failure points to useful documentation without recommending disabled SSL verification.