No common next protocol should fail handshake

Motiviation:
There is currently no means to fail the SSL handshake due to there being no common next protocol.
The current treatment of a  return value from  also results in no NextProtocolMessage being sent to the server.
According to [NPN RFC section 3](http://tools.ietf.org/html/draft-agl-tls-nextprotoneg-04#section-3) and [Google's NPN Spec, Next Protocol Negotiation Extension Section](https://technotes.googlecode.com/git/nextprotoneg.html)  if the server included a  extension.

Modifications:
-Returning  from  should result in a failed SSL handshake with alert no_application_protocol(120)
-Add unit test for this scenario

Result:
jetty npn-boot is compatible with specifications and allows a means to fail the handshake if no common next procotols found.

Signed-off-by: Scott Mitchell <scott.k.mitch1@gmail.com>
446672 - NPN Specification issue in the case no protocols are selected.

Clarified javadocs about the no protocol case, fixed javadocs example,
and small cosmetic changes.
[maven-release-plugin] prepare release npn-api-1.1.1.v20141010
[maven-release-plugin] prepare for next development iteration