ISPN-2935 After view change single node is left in cluster, but still tries to invoke stuff remotely

* Make the view listener synchronous and move the processing to an async
  transport thread.
* Synchronize the view handling on the coordinator.
* When recovering the cache status after becoming coordinator, remove cache
  members that are no longer cluster members. (Even though the member will
  be removed when the next view is handled.)
ISPN-2910 Divide by zero exception on shutdown

Skip topology update when a new node becomes coordinator and all the
members of a cache leave while the coordinator recovers the state.
ISPN-2966 NBST: Concurrent leavers can lead to deadlock

Make the CH_UPDATE and REBALANCE_START commands asynchronous (but keep them OOB).
State transfer code cleanup

* Rename StateTransferManager.notifyEndOfTopologyUpdate() to notifyEndOfRebalance() to reflect its actual purpose
* Remove unused method StateTransferManager.isLocalNodeFirst()
* Clarify javadoc LoLocalTopologyManager.confirmRebalance()
ISPN-2589 NPE in InvalidateL1Command

This NPE can appear in both DIST and REPL mode when we process a topology update in which the current node is not a member.

* There is no reason to invalidate segments if we are not a member, so the call to StateConsumerImpl.invalidateSegments() is guarded with a membership check. This also avoids the NPE.
* StateConsumerImpl.invalidateSegments() was wrongly using CommandsFactory.buildInvalidateFromL1Command where it should actually be buildInvalidateCommand()
* Extract all the logic to restart broken transfers from failed sources into a separate method (StateConsumerImpl.restartBrokenTransfers())
* Rename StateConsumerImpl.notifyEndOfTopologyUpdate() to notifyEndOfRebalanceIfNeeded() to clarify its purpose
* Remove StateConsumerImpl.activeTopologyUpdates member as all the logic regarding it has long become redundant
* Remove one of the overloaded variants of CommandsFactory.buildInvalidateFromL1Command that is no longer used
ISPN-3120 StateConsumerImpl can ignore state received during a rebalance

* Receiving state shouldn't finish the rebalance before all the added
  segments have a source.
* When all the owners of a segment leave and new owners are assigned, the
  new owners should not request state for those segments.