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.
Actually, version changes need not be synchronized because there is a coarser lock on the communication group that is acquired when changing state of the TaskNode (running/failed). And version is bumped when there is failure. Plus in the implementation it is an AtomicBoolean.