No merge on resolve

[AlexeyBarabash]

Fixes #261

With this PR resolve operation becomes much simpler. No merge is performed, always wins the latest record. From the other side, now the lib could not accept partial records, for example UPDATE record for bookmark with the only title field change, all fields should be specified even ones which remain the same.

[bridiver]

To be clear, partial updates were never intended to be supported and unnecessarily complicated the implementation

[darkdh]

we should also remove this workaround
20d7fd7

[darkdh]

why do we need to pull out these two DELETE cases?

[AlexeyBarabash]

I think, DELETE is a special case of the operation. When it happens, the object is destroyed and no more sense to perform any next operation on the object.

I chose DELETE wins way after considering this:

1. deviceA and deviceB both has synced bookmark bookmarkA
2. at almost the same time bookmarkA is renamed on deviceA and removed on deviceB
3. what would I expect?

I would expect bookmarkA will be removed on both devices, so I put this into the code.

And what do you think?

[darkdh]

we still need to consider timestamp because Android and brave-core now save object id even if the bookmark is deleted, which is the measure for preventing duplicate bookmarks when leaving and rejoining the sync chain. So DELETE still need to compete with CREATE or even UPDATE which is your case .

[AlexeyBarabash]

Closing as moving to sync v2