This is the execution ticket for SERVER-117460.

When dropping a collection it's possible to specify the UUID to drop like:

db.runCommand({drop: "xyz", collectionUUID: UUID("1234-5678")})

Since SERVER-116090, dropCollection uses acquireCollectionOrView from the Shard Role API so we can pass the expectedUUID in the collection acquisition and remove the current ad-hoc checks (see _checkUUIDAndReplState, checkCollectionUUIDMismatch in drop_collection.cpp).

There is an issue with this: viewful timeseries collections have a special behavior where they throw InvalidOptions rather than CollectionUUIDMismatch. We can change the behavior, or wait for 9.0 where viewful timeseries is removed.