ShardServerOpObserver is currently misused to commit metadata for createDatabaseand dropDatabase. Today, its role is to write to disk, populate the DSS, and log the 'c' oplog entry.

It should only be used to react to the oplog 'c' entry and not be used for installing database metadata in different components. By doing the last, we are decoupling sharding knowledge from the oplog.