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.
The need these are filling now is ultimately the `ProtocolSelector` and `ProtocolSelectedListener` are instantiated in a `JettyAlpnSslEngine` or `JettyNpnSslEngine` and interacts with the engine that instantiates them (by using the `setApplicationProtocol` method).  The way the code is structure now there will have to be some link between the two objects.  Can you clarify your suggestion?  Are you suggesting a different way to satisfy the dependency or a way to restructure and avoid this dependency?