Currently, the mechanism that provides idempotency for creating a collection acquires the collection to check its options after receiving a NamespaceExists error from the creation attempt. This means that there are two separate acquisitions that occur: once to try to create the collection, and once to check if the existing options are the same (with the collection being released in between). We may want to refactor this so that all of this can happen under a single collection acquisition.