Stop caching "originator_cache_guid" and "originator_client_item_id" to

[darkdh]

prevent generating duplicate tracking entries.
The cached ids are not accurate when receiving remote CREATE and then
committing UPDATE because we never get to propagate the real value to
other devices

Resolves brave/brave-browser#8203

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:

STR in brave/brave-browser#8203

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.

[bridiver]

++

[LaurenWags]

@btlechowski notes are here: brave/brave-browser#8203 (comment)

@LaurenWags notes:
Verified using

Brave	1.6.24 Chromium: 80.0.3987.100 (Official Build) nightly (64-bit)
Revision	3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864}
OS	macOS Version 10.14.6 (Build 18G103)

• Verified STR from 3 consecutive sync updates will result deletion brave-browser#8203
• Tested folder scenario first, URL scenario second
  Device A: macOS x64 10.14.6
  Device B: Ubuntu VM 16.04