Demonstration:

db = db.getSiblingDB("test");
db.createCollection( "weather", { timeseries: { timeField: "timestamp" } })
db.runCommand({insert:"weather", collectionUUID: UUID("12345678-1234-1234-1234-f776a983614f"), documents:[{timestamp: new Date()}]});

This risks data corruption in mongosync, which relies on `collectionUUID` to indicate when a collection has been renamed or dropped.

Previously I thought this was just a matter of the server deprioritizing CollectionUUIDMismatch errors (see JIRA history), but it’s worse.

Expected behavior: I would expect CollectionUUIDMismatch to be returned as with non-time-series collections.