In the MigrationSourceManager there is a check here that assumes if the shard has a chunk with the minKey, but doesn't have a maxKey corresponding to the command's maxKey, that the metadata is corrupted.

We should check whether there's another chunk with a minKey matching the maxKey, and if so, assume that the chunk was split and return a more benign error message.