This is so that we can create an instance of ShardLocal on the stack whenever we need to use it, rather than do all reads/writes through a single instance of ShardLocal.

The last optime is the only state that ShardLocal maintains, and rather than have ShardLocal and ReplicationCoordinator both maintain the latest optime, the ReplicationCoordinator should just be used by ShardLocal to get the latest optime.