There is a new privilege type forceUUID

This privilege is referenced in DOCS-11024 but we do not have documentation for it yet.

spencer.jackson provided info on the privilege via Slack

From the conversation:

If you could run applyOps, with a 'create' op, you could force a collection to come into being with a user specified UUID. But that's just how replication has to work, primaries must be able to create collections like that on secondaries.

Now, we also need a new privilege, for calling `create` with a user specified UUID. We could have just required Internal privileges, like those provided by __system, but it turns out you need this power to be attached to the `restore` role. When you do sharded restores, each shard needs to have the same UUID for the same collection. So, that's a new behavior, that you couldn't do before, that needs to be granularly handed out, that needs its own actiontype. That's what `forceUUID` is for.