After SERVER-115710, the listDatabases command on a sharded cluster started returning databases present in config.databases even if they no longer exist on any shard.

Since moveCollection can recreate a database entry in config.databases when it runs concurrently with dropDatabase, we can't assume the database won't exist when the balancer issues background moveCollection commands. Therefore, we need to update the test drop_database.js to stop making that assumption.