The server forbids some DDL operations, like shardCollection and drop, on time-series buckets collections. For most applications this is sensible, but it prevents mongosync from sending a `collectionUUID` when doing these operations.

For now that's OK because mongosync only does single-threaded DDL; however, as of REP-2924 mongosync will augment preexisting namespaces, which means we'll potentially have multiple mongosyncs syncing to the same collection.

Unless we're going to disavow data integrity for time-series in these situations, then, the server will need to allow mongosync to do full DDL on time-series bucket collections. These operations should all accept `collectionUUID` as well.

I envision that, as with SERVER-77003, the server will only allow this functionality to clients with the `restore` role.