Error when using accountId that does not exist (SEC_E_WRONG_PRINCIPAL)

[arthuraraujo-msft]

Reported by @JeffMill.

This error code is being returned by the SFSClientTool when using an accountId that does not exist.
Result code: ConnectionUnexpectedError. Message: schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL (0x80090322) - The target principal name is incorrect.

We should consider if this Curl error can be directly related to the accountId and transformed into a clearer message.

[arthuraraujo-msft]

Error will change once we switch to openssl

[arthuraraujo-msft]

Looks like on openssl this will fail with CURLE_PEER_FAILED_VERIFICATION and message "SSL certificate problem: self-signed certificate in certificate chain".
We can leverage https://curl.se/libcurl/c/[CURLINFO_SSL_VERIFYRESULT](https://curl.se/libcurl/c/CURLINFO_SSL_VERIFYRESULT.html).html.
The result is "19" in this case. This is likely an OpenSSL enum.

When the certificate is not correct but endpoint is, it will also fail with CURLE_PEER_FAILED_VERIFICATION, but message "SSL certificate problem: unable to get local issuer certificate". The CURLINFO_SSL_VERIFYRESULT is 20.

[arthuraraujo-msft]

Here is the source of the numbers
https://github.com/openssl/openssl/blob/master/include/openssl/x509_vfy.h.in#L226C1-L226C60
We can add our enum to check this.