SERVER-32643 adds a metadataOnly mode to Cloner::copyDb, to be used when clone is called by configsvrMovePrimary.

Currently, copyDb uses Cloner::filterOptionsForClone to select out the info to copy over to the new instance of the DB. At that point it drops the UUIDs, but when we are using clone for movePrimary, we want to keep the UUIDs consistent since it is all one collection.

We should change filterOptionsForClone so that when metadataOnly=true, we either
a) verify the UUIDs match if the collection already exists on the new primary, or
b) use the collection's UUID from the old primary when we create it for the first time on the new primary.