Currently, when DDLs that modify database metadata (such as createDB or movePrimary) need to contact a remote shard—which acts as the authoritative source of truth for that database—they use a ShardRemote by sending a write or delete command.

However, the new model (SPM-3729) also requires appending an oplog 'c' entry to notify secondaries to update the shard-local catalog cache. To address this, we need to design a new command that encapsulates this logic, enabling it to be sent to any shard to commit the database metadata update to the shard-local catalog.