A shard can keep stale collection filtering metadata (CSS/CSR) from a previous database incarnation after dropDatabase, and that stale state can conflict with the recreated database.

Proposed fix:

In the local createDatabase metadata commit path, after setting DSS for the database, iterate the known collection CSS namespaces for that DB and clear their collection metadata on the DB primary shard.

This should only be done on the new DB primary shard. Other shards can keep kUnowned for that DB until a future operation, such as chunk arrival or collection metadata commit, gives them ownership.