Zookeeper service member sabotage fix

This is impossible to gracefully recover from an improperly configured service member in Zookeeper. We cannot ignore it, this is maybe a legit service member and ignoring it would alter the ring token ranges. On the other hand we cannot really include it in the ring (and force it to down), this may not be a legit service member after all and including it also result to improper ring ranges.

This fix prevent the cluster to start (i.e. fail synchronously). If the cluster is already running when the rogue service member appears, all service members of the affected service are forced Down. The other services are not affected.

This solution prevent corruption and ensure alarms are raised if the service member status are monitored.