Changes for next gen group communication

Contains necessary changes for next gen group communication primitives.
We allow the notion of arbitrary number of named communication groups
containing an arbitrary number of named operators. Supports a simple API
to get topology changes & update the topology. Also supports a simple
ramp-up mode by specifying the minimum number of tasks in a
communication group.
Would it make sense to make `NamingMessage` immutable by passing in the link at construction time?