Moved the version properties to the parent POM.
Initial import of the Netty STOMP server implementation.
Moved the version properties to the parent POM.
Fixed some bugs and implemented a client/server example application.
Switch over to using netty-stomp as the STOMP server and client.

- Ported the HazelcastMQ STOMP Server over to using netty-stomp rather than implementing a full 
STOMP server internally. 
- Updated the examples to use the BasicStompClient from netty-stomp.
- Started to remove the HazelcastMQ STOMP Shared and Client modules.
Fixed an issue in the properties defining the compiler target version.
Ported the STOMP server implementation to use a "stomplet" API.

The stomplet API allows for a single channel handler to be installed in Netty and it abstracts away
all the Netty specific interaction. With a single handler, it is now much easier to understand the
order of execution and to make sure the pipeline is properly terminated. The same work needs
to be done on the client side.
Rewrite the STOMP client API to support frame listeners for all frame types.
Added a queuing frame listener to support synchronous/blocking frame handling on the client.
Update the examples.
Renamed the netty-stomp module to Yeti to give it an easy to remember name
and to open the possibility of different network frameworks in the future.
Updated the README to include Yeti documentation.
Converted the Frame class to be immutable which is a little safer. The FrameBuilder now 
provides the dynamic frame construction functionality.