Consider removing the "Exceeded retries count trying to get consistent keys/values for config replication" log message

We should consider removing this log trace. In issue MB-43518 (and MB-44598 which looks to be essentially the same issue) I conclude that despite the fact that the log trace is shown, on balance we should not alter the config synchronization logic. I think the current logic strikes a good balance of attempting to batch changes and not waiting too long to do so. And at least I can't think of a better arrangement.

Note this will all go away when we move metakv to chronicle.