Removing Nodes

When subnet node slots become full, there must be a way to remove nodes that are the lowest performing if other nodes are in the queue that are higher-performing.

Registered (see classifications) nodes that are in the queue can only be activated once a slot is available. If a registered node in the queue is evaluated in the subnet to be higher-performing than a currently active subnet node, the node that is lower-performing should be left out of the consensus data for its penalties to accrue until it's removed (see maximum penalties). This will create room by opening a slot for one of the registered subnet nodes that are in the queue to become activated to take their place.