Add support for aggregated destination

[olegz]

There are times when a consumer destination may be represented by several physical destinations. And while this is actually already supported by the framework, the actual mechanism creates multiple listener containers per each destination which may not be the most optimal solution.

Aggregate destination will allow one to identify which physical destination should be handled by a single listener container.

See more details in the discussion here