Disable history sync datatype to fallback to typed urls datatype

[AlexeyBarabash]

Related Chromium change:
https://source.chromium.org/chromium/chromium/src/+/874f434296a6d02c9a2adcc5c664aa7915bf8681

Enable SyncEnableHistoryDataType by default

Bug: 1318028
Change-Id: Iee7539bb25c41279f333558934a3438e51487a71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4055561

Resolves brave/brave-browser#32857

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 lint, 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/Custom-Headers
  • 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:

[darkdh]

This would be just a workaround right?
I think we need to investigate in HistoryDataType because I can foresee typed url data type will go away sooner or later. Please open an issue for that.

[AlexeyBarabash]

yes this is a workaround to fix CR117 regression.

Proper solution is on the way, some investigations were done at #17216.

Created issue: brave/brave-browser#32876

[Uni-verse]

Verified on Samsung Galaxy S21 using version:

Brave	1.60.11 Chromium: 117.0.5938.48 (Official Build) canary (32-bit) 
Revision	31e5a6923b9af06a63afc70bd2907933cfd26df7
OS	Android 13; Build/TP1A.220624.014; 33; REL

• Verified STR in History is not synced on fresh profile [C117] brave-browser#32857 (comment) and ensured bookmarks, passwords and open tabs are syncing.
• Verified typed history is showing up in History page after joining sync chain and enabling history sync on new profile.

Example	Example	Example