Removed member higher prio than Exiting/Down, see #3309

I have not really been able to reproduce this, but this is my theory...

* ClusterSingletonManagerSpec revealed a bug in Gossip merge, which
  caused a removed member to come back into the member set after
  a gossip merge.
* Removed entry should have higher prio than Exiting, and Down in unreachable