SERVER-52778 added a scoped object to mark all codepaths that should be allowed to create a collection on shards. If the scoped object is not instantiated, when the shard server op observer reacts to a collection creation it throws an exception that is handled.

Since the shard server op observer is initialized merely on the base that a mongod has been spawned with the --shardsvr option, it throws the exception even when a mongod has not yet been promoted to shard.

The FLE2 cleanup and compact operations are creating/renaming collections but are not instantiating the scoped object (example). This ticket is to assess whether we want to support this corner case.