When removeShard is called during a step-up/step-down, the primary config node could finish removing the shard, but not return the response.

In this case, the next time removeShard is called, the new primary config node will return ShardNotFound instead of DrainingStatus::Completed, since the shard has already been removed.