Fix for 1873 : ServerState should be updated after a server crash

The ServerState is saved to the database periodically,
therefore in case of crash it is possible that is does not contain
the latest changes that have been processed and saved to the
database.
In order to make sure that the replication never looses changes,
when replication starts the server needs to search all the entries
that have been updated after the last write of the ServerState.
This is done by using the HistoricalCsnOrderingMatchingRule.