Currently for sharded clusters collmod, drop collection, drop database, refine collection shard key and rename uses the ConfigsvrSetAllowMigration command to leave the cluster in a steady state regarding migrations before doing any metadata change.

The command was done in SERVER-53861 in a time where PM-2210 was not implemented so it was not possible running cluster wide transactions internally. We can now deprecate the ConfigsvrSetAllowMigrations command and move it's implementation to every DDL coordinator using a remote transaction with the internal API.