Drive: udpate on a document just registered as a synchronization root is not taken into account

In fact the bug occurs since NXP-13425: "disableAuditLogger" is set to true in the context data of a document registered as a synchronization root. If one doesn't navigate to another document after registering it as a synchronization root and directly updates its title or some other property, as the document is not invalidated in the Seam context, "disableAuditLogger" sticks and the "documentModified" event doesn't get logged.