Requested Changes Connection API

[cb0s]

In a conversation with @fussel178 we noticed that the following things should be implemented as soon as possible to make the new connection API more useable.

• Remove "rework" from package name to ensure that there will be only one breaking change as soon as the old API vanishes (as stated in Clean Connection API #267)
• Add documentation to make the concept and the usage of the API more clear (currently it is very complicated to understand and might not be used in the intended way)
• Add broadcast functionality
  • For one specific interface type
  • For all net-interfaces
• Publish when new TCP-connection has been established (with the correct tcp-details, to inform everybody of the new connection which can be addressed)
• TcpDispatcher: Make config loading possible (e.g. with "FactoryVerticle" whose job is to deploy all the other required verticles)
• Add package-info where required

[cb0s]

@fussel178 @jvpichowski @pklaschka what do you think? Should there be a "message" on the eventBus if a packet gets dropped? There are special cases (e.g. when the client refuses as it closed the connection) where it might be useful to at least have the possibility to react on it.
Do you think this could be useful?