Right now, the test exercises commands on the timeseries view namespace fail with CollectionUUIDMismatch when run with a non-existent collection uuid and the uuid of the underlying buckets collection. 

We can expand the test to ensure the following scenarios return the expected CollectionUUIDMismatch response:

• All commands run with the UUID of an existing collection
• All commands run on the buckets namespace with a non-existent UUID and that of an existing collection
• All commands run on a pre-existing collection with the buckets collection UUID
• All commands run on a non-existent collection with the buckets collection UUID
• Test other commands that accept a 'collectionUUID' field such as
  • aggregate
  • dropCollection
  • dropIndexes
  • createIndexes
  • etc.