This project changed getting the config shard from the shard registry on the config server to return a ShardRemote instead of a ShardLocal. This means operations that were previously always process local, may now target other config server nodes. This could be problematic, e.g. if code relies on receiving a replication state change error after a failover, but now will retarget the new primary. We should audit visually and via invariants, etc. that all uses of ShardLocal before SERVER-71891 are safe to use ShardRemote.