Ignore bookmark icon url when browser gets bookmark form sync cloud

[AlexeyBarabash]

Intended t o fix brave/brave-browser#7893

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Android
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that these changes pass automated tests (unit, browser, security tests) on
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that all lint errors/warnings are resolved (npm run lint)
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone
• Public documentation has been updated as necessary. For instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protection-Mode
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-compatibility-issues-with-tracking-protection
  • https://github.com/brave/brave-browser/wiki/QA-Guide

Test Plan:

See steps in brave/brave-browser#7893

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on.
• All relevant documentation has been updated.

[AlexeyBarabash]

Some details.
Seeing

[9788:9788:0124/132232.884549:ERROR:bookmark_specifics_conversions.cc(295)] Invalid bookmark: specifics cannot have an icon_url without having a favicon.

which get us into https://source.chromium.org/chromium/chromium/src/+/79.0.3945.130:components/sync_bookmarks/bookmark_specifics_conversions.cc;l=295

[AlexeyBarabash]

Chromium sends both icon_url and icon_data in the same time and expects to have them either both or either none of them.

Here is a place where Chromium creates BookmarkSpecifics with icon data.

sync_pb::EntitySpecifics CreateSpecificsFromBookmarkNode(
    const bookmarks::BookmarkNode* node,
    bookmarks::BookmarkModel* model,
    bool force_favicon_load)

https://source.chromium.org/chromium/chromium/src/+/79.0.3945.130:components/sync_bookmarks/bookmark_specifics_conversions.cc;bpv=1;bpt=1;l=134

force_favicon_load is set to false only in tests.

It was a time when we put bookmark icon data into SyncRecord metadata to allow to get the boookmark instantly.
We reverted that at the that time because:

1. S3 sync records for bookmarks with icons became too big as for a simple sync record;
2. There were a cases when client tried to sending update record and that mixed with newly came sync record making mess;
3. Mobile clients in anyway does not send icon bitmap, as it is not in our spec.

I marking this PR as ready for review to allow issue be fixed asap. For the matter of icon, I creating a new issue just found brave/brave-browser#4095 (comment), we are good to load icon once the page will be visited.

[bsclifton]

Merging as this is required to unblock some items for 1.3. CI has passed and PR has been peer reviewed 😄👍