Consider the following scenario to transitionToDedicatedConfigServer.
1. config shard is marked to start draining
2. The last chunk is moved out from the config shard
3. The last orphan is cleaned up
4. Once all the chunks/orphans are cleaned, all the dbs are dropped.
5. Remove entry from (config.shards)

If a ddl operation(drop or rename) is received before step 5, we will send drop/rename to all shards which takes a critical section lock on all the shards. And if the ddl operation completes after step 5, we might leave a lingering lock on config server since the release is sent to all shard (config server isn't a shard anymore).

This ticket is to add a workaround fix where when the critical section is released for drop/rename - include configServer in all shards list.

Also, consider/evaluate other DDLs as time permits