ALPN / NPN need to handle no compatible protocols found

Motivation:
If there are no common protocols in the ALPN protocol exchange we still compete the handshake successfully.  This handshake should fail according to http://tools.ietf.org/html/rfc7301#section-3.2 with a status of no_application_protocol.

Modifications:
-Upstream project used for ALPN (alpn-boot) does not support this.  So a PR https://github.com/jetty-project/jetty-alpn/pull/3 was submitted.
-The netty code using alpn-boot should support the new interface (return null on existing method).
-Version number of alpn-boot must be updated in pom.xml files

Result:
-Netty fails the SSL handshake if ALPN is used and there are no common protocols.
Yah I'm pretty far into the whatifs.  The use case I'm thinking of is if OpenSSL needs additional elements to be constructed.  OpenSSL could potentially subclass the factories and add new factory methods that only exist in the OpenSSL realm.  Not sure if this makes sense...anyways I think I'll take your suggestion.