Insert with collectionUUID could implicitly create a collection if command failed with collectionUUIDMismatch

This is not ideal because one large use case of using collectionUUID is that user might not know the actual collection name and relies on retrying CollectionUUIDMismatch error to tell the actual collection name, but having to deal with this side effect doesn't seem like a good user experience.

See the full slack discussion here.