issue 2119 : replication servers do not connect to each other when using setup

When using the setup to configure 2 servers in multimaster mode.
The setup first creates the configuration of the first server and start it
When the second setup is run to configure the second server, the setup updates
the configuration of the replication-server on the first server, however the code for handling this dynamic configuration was not yet written and this
information is not taken into account.

The replication servers are therefore not connected and the replication server
on the new host therefore does not get the updates.

These changes implement the dynamic configuration of replication servers so that
the same scenario works fine.

The only properties that is now not dynamically configurable is the
path of the changelog database.

A new test has been added for these changes.
I've also tested manually that this does fix the replication server problem
after configuration using the setup program.