align X509_VERIFY_PARAM host and email behavior with OpenSSL

[samuel40791765]

Issues:

Resolves CryptoAlg-1865

Description of changes:

A dig into some of the mySQL/AWS-LC test failures revealed that this was the root cause.

• https://github.com/mysql/mysql-server/blob/8.0/router/src/harness/src/tls_client_context.cc#L100
• https://github.com/mysql/mysql-server/blob/8.0/vio/viosslfactories.cc#L709

BoringSSL briefly made this backwards compatible, but enforced the stricter check a week later since Chrome was not effected by this.

• e759a9c
• 1902d81

This doesn't apply to us however, so we're reverting the strict check in an attempt to be more compatible with OpenSSL.

Call-outs:

I've reverted the check for X509_VERIFY_PARAM_set1_email while I was at it as well. X509_VERIFY_PARAM_set1_ip was using the same underlying logic as X509_VERIFY_PARAM_set1_email which made things a bit complicated.
X509_VERIFY_PARAM_set1_ip takes an unsigned char *, but changes to make it more compatible with OpenSSL required strlen to detect the length of the string. I've separated the logic for X509_VERIFY_PARAM_set1_email/ip into two functions to get around this.
X509_VERIFY_PARAM_set1_ip now maintains the original BoringSSL behavior, while X509_VERIFY_PARAM_set1_email is compatible with OpenSSL now. We can look into making X509_VERIFY_PARAM_set1_ip more compatible with OpenSSL later on if needed.

Testing:

CI

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.