small improvement in the replication monitoring

The replication monitoring was showing information for
- the replication domains
- the remote LDAP servers connected to the replication server
- the remote replication server connected to the replication server

but does not show any information for a local replication server.
A replication server that is started but does not have any server connected yet
therefore does not publish any monitoring information.

This changes add a new monitoring entry that fixes this lack and also change the names
of the monitoring entries of the server connected to the replication server to include the
"remote" keyword.

As an example, the monitoring information of a server that is also its replication server now looks like this :

dn: cn=Replication Server 8989 1,cn=monitor
objectClass: extensibleObject
objectClass: top
objectClass: ds-monitor-entry
replication server id: 1
replication server port: 8989
base-dn: dc=example,dc=com
cn: Replication Server 8989 1

dn: cn=Replication plugin dc=example\,dc=com,cn=monitor
objectClass: extensibleObject
objectClass: top
objectClass: ds-monitor-entry
lost-connections: 0
connected-to: localhost/127.0.0.1:8989
resolved-naming-conflicts: 0
replayed-updates: 0
base-dn: dc=example,dc=com
unresolved-naming-conflicts: 0
max-send-window: 100
max-rcv-window: 100
resolved-modify-conflicts: 0
current-send-window: 100
cn: Replication plugin dc=example,dc=com
pending-updates: 0
sent-updates: 0
received-updates: 0
current-rcv-window: 100
replayed-updates-ok: 0

dn: cn=Remote LDAP Server dc=example\,dc=com furon 1,cn=monitor
objectClass: extensibleObject
objectClass: top
objectClass: ds-monitor-entry
approximate-delay: 0
max-waiting-changes: 10000
update-sent: 0
waiting-changes: 0
update-received: 0
base-dn: dc=example,dc=com
update-waiting-acks: 0
max-send-window: 100
ack-received: 0
max-rcv-window: 100
current-send-window: 100
cn: Remote LDAP Server dc=example,dc=com furon 1
server-id: 1
LDAP-Server: furon
current-rcv-window: 100
ack-sent: 0