NiFiHostnameVerifier should be replaced

The NiFiHostnameVerifier does not handle wildcard certificates or complex SubjectAlternativeNames. It should be replaced with a more full-featured implementation, like OkHostnameVerifier from okhttp or DefaultHostnameVerifier from http-client. Either of these options requires introducing a new Maven dependency to nifi-commons and requires further investigation.

*Note: * the sun.net.www.protocol.httpsDefaultHostnameVerifier simply returns false on all inputs and is not a valid solution.