Don't truncate trailing zeroes in reqStart/reqEnd timestamps

Check for BVISNULL, maybe rootDSE is a valid reqDN

Add matching rules for all cases where it was missing.  Cleanup
incorrect types for a few attributes as well.  Fix network-timeout
handling in back-ldap/meta/asyncmeta.

Restructure response/cleanup invocation to avoid cleanup happening before response

And try another approach. Always write contextCSN updates, but
don't set dont_replicate for updates we want propagated.

Update syncprov contextCSNs when context entry is added.
Fix accesslog to properly tag Add op when adding context entry.

Ondřej Kuzník authored Apr 04, 2017 and Quanah Gibson-Mount committed Apr 07, 2017

Make two successive modifications of the same attribute separate. This
lets the consumer interpret the log entry the same way as the server
that produced it.

Still depends on the log entry attributes being read in the same order
as they were written.

accesslog can alter the timestamp on contextCSN updates

Prevent spurious contextCSN generation
and ignore consumers when we have no contextCSN yet.
But make sure to propagate valid contextCSN updates to
accesslog/syncprov for delta consumers.