SERVER-131694 changed the logic of the authoritative metadata cloning DDL so that it targets not only shards that currently own chunks, but also shards that historically owned chunks (even if currently they own none).

However it's possible that an historical owner shard has since been removed via removeShard. In this case we will try to target a removed shard so the cloning DDL will return a ShardNotFound error, triggering an infinite retry loop.