Dropping the collection(s) containing shard split or tenant migration/merge state document result in deleting all tenant access blockers shard split tenant migration.

When we'll have both merge and split active, this will cause issues as dropping collection for one could remove blockers for the other (which could have an active operation).

A solution would be to prevent dropping either collection in serverless mode. If a user wants to delete the collection (for maintenance, dealing with issues, etc), the node can be restarted in non-serverless mode.