Enable custom host name verifier

[zqmmqz]

Describe the feature

NetClientOptions now support specific algorithm for host name verification.
Is it possible to support custom host name similar to the uses of javax.net.ssl.HostnameVerifier?

Use cases

Besides the default verification which compares the common name in the SubjectDN in the SSL server's digital certificate with the host name of the SSL server, one would want to verify other behaviors.

My uses case is that we use a vertx client to talk to a server whose cert's common name isn't a valid host name. So we want to verify one fixed field in the SubjectDN. Currently we disable the host name verification to skip this because vertx asks a specific algorithm for the verification, but our case needs a more complex logic.

[vietj]

not sure it is possible (depending on the hooks in Netty for this)

[tsegismont]

This might be useful for the Reactive MSSQL Client too: when a server redirects the client to another server (with TDS ROUTING token), the hostname provided for connection may not be the same as of the actual server.

[tsegismont]

Duplicates #3720

It is already possible to customize verification. Create a TrustManager instance and then custom TrustOptions with wrap.