Move nodes in membership to removed when ready to do so

[ktoso]

We need to decide when it is safe to move a node do removed and do so, otherwise we'll continue gossiping dead nodes like we do now:

ping(
    lastKnownStatus: DistributedActors.SWIM.Status.alive(incarnation: 0),
    replyTo: ActorRef<SWIM.Ack>(/user / $ask - e),
    payload: DistributedActors.SWIM.Payload.membership([
        DistributedActors.SWIMMember(ref: ActorRef<SWIM.Message>(sact://SERVANT@127.0.0.1:7343/system/swim), status: DistributedActors.SWIM.Status.alive(incarnation: 0), protocolPeriod: 2),
        DistributedActors.SWIMMember(ref: ActorRef<SWIM.Message>(sact://SERVANT@127.0.0.1:7342/system/swim), status: DistributedActors.SWIM.Status.alive(incarnation: 0), protocolPeriod: 2),
        DistributedActors.SWIMMember(ref: ActorRef<SWIM.Message>(sact://SERVANT@127.0.0.1:7340/system/swim), status: DistributedActors.SWIM.Status.dead, protocolPeriod: 2),
        DistributedActors.SWIMMember(ref: ActorRef<SWIM.Message>(sact://SERVANT@127.0.0.1:7341/system/swim), status: DistributedActors.SWIM.Status.dead, protocolPeriod: 2),
        DistributedActors.SWIMMember(ref: ActorRef<SWIM.Message>(sact://SERVANT@127.0.0.1:7338/system/swim), status: DistributedActors.SWIM.Status.dead, protocolPeriod: 1),
        DistributedActors.SWIMMember(ref: ActorRef<SWIM.Message>(sact://SERVANT@127.0.0.1:7339/system/swim), status: DistributedActors.SWIM.Status.dead, protocolPeriod: 1)
    ]))

[ktoso]

Bumping importance (pick next) with the new gossip this is doable correctly