HORNETQ-1414 Allow exclusions/list on cluster addr

Adds the ability to support more than just a single string for matching
addresses on cluster connections.  Cluster connection address can now
consist of a list of strings that are used as filters, any of which can
be matched against the address.  In addition a new exclusion syntax '!'
is now supported that allows users to explicitly ignore any address
matching anything following '!'.

For example: 'jms.eu,!jms.eu.uk' will match all addresses beginning with
jms.eu except for those beginning with jms.eu.uk.
Merge pull request #1891 from jbertram/master

HORNETQ-1425 Increasing coverage of fluent API
Merge pull request #1881 from mtaylor/HORNETQ-1414

HORNETQ-1414 Allow exclusions/list on cluster addr
updating bytemant to the latest (2.2.20)
BZ-1149936 HORNETQ-1427 Avoid orphaned consumers

https://issues.jboss.org/browse/HORNETQ-1427
https://bugzilla.redhat.com/show_bug.cgi?id=1149936

We have been reported about orphaned consumers cases.
The only cases where I saw this possibly happening was during a hypotethical
exception during server.close() or during a temporary blocking client (thread waiting to lock)

To avoid that I'm now removing connections at the end of loops and making the exception treatment
per consumer, so if any exception happened we will continue closing. at the worst case the connection
will still be on the maps and this won't be na issue any longer.
Merge pull request #1893 from clebertsuconic/master

BZ-1149936 HORNETQ-1427 Avoid orphaned consumers
test fix
Merge pull request #1895 from andytaylor/master

test fix
test fix on TemporaryQueueTest

The test is now closing connections at the end. the previous assertion needed to be adapted
Merge pull request #1898 from clebertsuconic/master

test fix on TemporaryQueueTest
HORNETQ-1429 Major refactoring on AMQP and client APIS

https://issues.jboss.org/browse/HORNETQ-1429

This is doing a major refactoring on AMQP:
- Introducing ProtonPlug.
 At the moment ProtonPlug is part of master as it will be easier to manage it this way.
 We could eventually make it an independent project
- Support on Flow control
 The server will take flow control credits out of the server and the server
 won't deliver messages when out of the credits
 There will be some space for flow control but we can do it at a later point
- Client refactoring - ready for multi protocol on the client
 I'm keeping things like consumerID blunt, making it ready for a future integration on the client
 I intended to have amqp client as part of this commit but i couldn't finish it at the time
 the refactoring at the client will be kept here case we decide to resume AMQP on the client later.
- There are a few other tweaks done as part of this refactoring that made things easier
  such as properly implement IDGenerator on the JOurnal instead of using a separate interface
Merge pull request #1899 from clebertsuconic/amqp-new

HORNETQ-1429 Major refactoring on AMQP and client APIS
meta data for project
HORNETQ-1414 Allow exclusions/list on cluster addr

this adds to https://github.com/hornetq/hornetq/commit/ee09bfdea58ee34bb45afdda7154489232265143

update sendQueueInfoToQueue on PostOfficeImpl to also use the same filter.
Merge pull request #1901 from andytaylor/master

meta data for project
small doc formatting fix
HORNETQ-1430 Encoding/decoding not working for colons in STOMP headers