Use external ID to match native model nodes during bookmark association.

Use external ID to match native model nodes during bookmark association.

This is a resubmit of https://codereview.chromium.org/904083002
which was reverted due to an unrelated flaky test. There are no
changes compared to the original patch, hence skipping the code
review (zea@ was the original reviewer).

Original patch description:

The fix improves matching of nodes in BookmarkModelAssociator in
situations where there are multiple bookmarks or folders with the
same titles or URLs.
This will address one particular scenario leading to bookmark
duplication (see crbug.com/118105).

1) In BookmarkModelAssociator::BuildAssociations, when there are
multiple native model nodes with matching title / URL, a secondary
match on external ID is used to pick a preferred one; otherwise
the first matching node is returned.
The preferred match on external ID should be applicable in most
situations except when the native model has been rebuilt from scratch.
Picking a wrong folder during the association process results in
duplicating the entire subtree within the wrong folder. This issue
should be addressed now.
2) In BookmarkModelAssociator::ApplyDeletesFromSyncJournal the external
ID match is now the primary criteria for selecting a native model
node to be deleted. The previous implementation would pick an arbitrary
native model node based on just the title / URL match anywhere in the
node hierarchy. That would happen every time after deleting a bookmark
or folder and recreating it in another place.
Since external IDs might be reused, there is a secondary match on
title and URL to ensure that the right node gets deleted. To avoid
costly O(N*M) algorithm (where N is number of bookmarks and M is
number of entries in delete journal), the implementation uses a set
of external IDs to reduce the cost to O(N*logM).

BUG=456228
TBR=zea@chromium.org

Committed: https://crrev.com/8fab3e6090c48042d3d6810c1ef900e39bcc730c
Cr-Commit-Position: refs/heads/master@{#317688}

[stanisc, 2015-02-10 18:31:29]

Patchset #1 (id:1) has been deleted

[stanisc, 2015-02-20 21:38:24]

stanisc@chromium.org changed reviewers:
+ zea@chromium.org

[stanisc, 2015-02-23 23:59:29]

The CQ bit was checked by stanisc@chromium.org

[commit-bot: I haz the power, 2015-02-24 00:01:33]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/912693002/20001

[commit-bot: I haz the power, 2015-02-24 00:26:38]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2015-02-24 00:27:52]

Patchset 1 (id:??) landed as
https://crrev.com/8fab3e6090c48042d3d6810c1ef900e39bcc730c
Cr-Commit-Position: refs/heads/master@{#317688}