Fix use after move in sharding_util::processShardResponses

In sharding_util::processShardResponses we std::move part of the response and then we std::move again the entire response object.

This is not causing invalid memory access because the RemoteCommandResponse class doesn't have a move constructor, thus the first std::move is actually making a copy of the object.