Fixing a few tests with issues on asynchronous .getMessageCount

We have recently changed getMessageCount to not flush on executors any longer, but some of our tests were expecting that behaviour. for that reason I replaced a few calls to .getMessageCount() to some method that will do the old semantic.
AMQP Multi Protocol support
Refactoring text / map out of HornetQMessage into an utility class
more utilities
converter
Refactoring conversion
convertion refactoring
refactoring jms and amqp
simple fix
fixing binary
fixing byte message through protonTest
tests
fixes
Implementing conversion of MapMessages
fixes
Text messages amqp
fix
default message type
Stream messages
more fixes