This scoped object allows a caller to create a collection outside of the sharding subsystem. However, it does not take a namespace and thus under this object, the caller can create any and as many collections as they wish. This is problematic for our efforts to track replica set DDLs as we need to know not only that a collection is being created but also which collection is being created.

In this ticket, we will introduce a namespace to this scoped object and enforce in the op observer that the collection being created is the one for which the scoped object was acquired. Likely this will require an exception for timeseries collections.