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.
@normanmaurer - The method javadocs indicate the signature allows and will handle any throwable object.  This was done largely to be consistent and avoid duplication of catching/rethrowing for jetty interfaces....and also using the concept of no matter what is thrown it should be caught. I think part of the justification the jetty folks used was having `throws Throwable` may be considered bad practice....