Infrastructure

Mutable Member Nodes that only retain the latest version of their entities rarely do the bookkeeping work on orphaned versions they no longer host. This includes:

1. setting the obsoletedBy field of the the orphaned object
2. transferring authority to another node (CN or MN)
3. invalidating the replica in the Replica section

This leads to problems in search, resolve, and updating system metadata.

I propose we utilize the new CN-carve-out Node Properties to enable the CN to perform these actions on the mutable member node's behalf. This can either be done with a blanket property 'isMutable', or something more specific, because some member nodes might orphan the object, but keep the system metadata. 'autoObsolete', 'autoDeorphan', 'autoReplicaAudit', or such...