Avoid simultaneous KDB/ulog locks in ulog_replay

In ulog_replay(), instead of locking the KDB and ulog for the whole
operation, separately lock and update the ulog after each database
update, as we would for a locally initiated database operation (after
commit 444ef5fe9ec8d64a5db27b3a8aaf6813dd7ef0e0).

https://github.com/krb5/krb5/commit/682013f55984173f2f742c0ecf43d83181100456
Author: Greg Hudson <ghudson@mit.edu>
Commit: 682013f55984173f2f742c0ecf43d83181100456
Branch: master
 src/lib/kdb/kdb_log.c |   32 ++++++++++++++------------------
 1 files changed, 14 insertions(+), 18 deletions(-)