Defragmentation action objects are unnecessarily copied while processed by the Balancer

The logic implemented by the balancer to retrieve, submit and acknowledge defragmentation commands from the policy involves multiple object copies (1, 2) that could be replaced with {{std::move()}}s.

The case of SplitInfo is particularly problematic, as it might involve the copy of a std::vector<BSONObjs> containing thousands of elements.