createIndex may end up creating an "orphaned" bucket collection (with default empty collection options) when executed concurrently with dropCollection.

1. Create a timeseries collection
2. Create index starts (translates view ns to bucket ns)
3. Drop collection starts
4. Drop collection succeeds
5. Create index continues (timeseries not existing anymore)
6. Create index implicitly creates the bucket collection
7. Create index succeeds

Reproducible attached (including diff to apply on ae89abf235 to add a failpoint during create index).

As part of this ticket we should be able to add `createIndex` to create_all_type_collections.js concurrency test