Random migration on unsharded collections (insde a failpoint) always picks migrations before sharding policy.
Additionally, a shard that picks one migration cannot do more migrations. So, for tests with two shards it is common that the unsharded policy dominates the sharded one, and may produce starvation of sharded migrations.

The puropuse of this ticket is to introduce a simple mechanism for testing that allows both types of migrations.