Fixed device duplication when Google Account cookies are deleted

[AlexeyBarabash]

This PR disables upstream's methods

SyncServiceImpl::OnAccountsCookieDeletedByUserAction()
SyncServiceImpl::OnAccountsInCookieUpdated()
SyncServiceImpl::OnPrimaryAccountChanged()

to prevent re-creating of Sync Client ID and device duplication in a Sync chain.

Resolves brave/brave-browser#41615

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

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, 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-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

I. Scenario with manual logout from GMail

1. Add devices A and B into the sync chain
2. On device B login into GMail
3. On device B logout from GMail
4. Restart browser on Device B
5. Expected device B is not duplicated at A's list

II. Scenario with Delete sites data option

1. Add devices A and B into the sync chain
2. On device B login into GMail
3. On device B go to brave://settings/content/siteData and choose

Delete data sites have saved to your device when you close all windows
Sites will probably work as you expect but won't remember you after you close all Brave windows

4. Restart browser on Device B
5. Expected device B is not duplicated at A's list

[github-actions]

The security team is monitoring all repositories for certain keywords. This PR includes the word(s) "login" and so security team members have been added as reviewers to take a look.

No need to request a full security review at this stage, the security team will take a look shortly and either clear the label or request more information/changes.

Notifications have already been sent, but if this is blocking your merge feel free to reach out directly to the security team on Slack so that we can expedite this check.

[kdenhartog]

Looks fine to me, removing the needs-security-review label

[bridiver]

approving as code owner for chromium_src