Fix for issue 2870: status and dsreplication status do not show replication monitoring
The changes consist basically in using the new attributes
"approx-older-change-not-synchronized-millis" and "missing-changes" in status and replication status command-lines.  In fact a millisecond version of approx-older-change-not-synchronized-millis has been added in order the remote command-line to be able to provide a localized version of the date (instead of directly presenting the date that was written by the server).

The code has been updated to take into consideration the fact that there is information for several servers; so the replication domain id is used to discriminate the information of the different servers.