The logs emitted by ShardingDDLCoordinator infrastructure (e.g. retry, error, ...) only contains the coordinator ID.

Many coordinators contains specific parameters that could help in the debugging process, for instance when a movePrimary fails it would be useful to know also which was the destination shard.

We could achieve by exposing a function similar to appendComamndInfo that instead of appending to a BSONObjBuilder appends elements to a mongo::logv2::DynamicAttributes.