Enable History datatype for Sync

[AlexeyBarabash]

Resolves brave/brave-browser#32876

This PR enables History datatype in Brave, becasue after CR119 the old TypedUrls datatype, which was used for History Sync, is wiped out from Chromium codebase.

Related server PR brave/go-sync#176 .

Key points of the PR:

• reverts the PRs which were using TypedUrl: PR#16705 (Sync all history), PR#16478 (Display history sync diagnostic info), PR#20071 (Disable history sync datatype to fallback to typed urls datatype);
• Overrides HistoryModelTypeController and HistoryDeleteDirectivesModelTypeController to allow start when encrypt everything option is enabled;
• HISTORY datatype is included into encrypteble types, so only clients in the chain can see raw urls, server can't;
• HISTORY_DELETE_DIRECTIVES is kept unencrypted, because it is a technical data; HistoryDeleteDirectiveSpecifics::UrlDirective::url field is forcibly cleaned out not to leak, chrome.history.deleteUrl extension API will not work properly;
• modified LowPriorityUserTypes - HISTORY is removed, HISTORY_DELETE_DIRECTIVES added. We need this to make device first download History and then delete directives download and apply after. This patch will be reverted when the server will support delete directives.

Note: history entries created before enabling sync and turn history type on will not be sent to the server - inherited from upstream behavior .

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have [requested] . Requested https://github.com/brave/reviews/issues/1427
• 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:

Please note, this PR requires updated server, either built from brave/go-sync#176 or wait till it will be merged/deployed.

I. Browse/manual remove history entries

1. Enable Sync on deviceA, turn on History datatype;
2. Join deviceB to the chain, also turn on History datatype;
3. From deviceA visit urls
   https://search.brave.com/search?q=1000001&source=web
   https://search.brave.com/search?q=1000002&source=web
   https://search.brave.com/search?q=1000003&source=web
4. From deviceB visit urls
   https://search.brave.com/search?q=2000001&source=web
   https://search.brave.com/search?q=2000002&source=web
   https://search.brave.com/search?q=2000003&source=web
5. Ensure both devices have those urls in history. Maybe need to wait ~1 minute max.
6. From deviceA remove https://search.brave.com/search?q=2000002&source=web url from history; from deviceB remove https://search.brave.com/search?q=1000002&source=web url from history;
7. Wait a little (< 1min), refresh history pages. Expected not to have https://search.brave.com/search?q=2000002&source=web and https://search.brave.com/search?q=1000002&source=web on both devices.
8. Join deviceC to the sync chain, enable history
9. Check brave://history page on deviceC - expected not to have urls https://search.brave.com/search?q=2000002&source=web , https://search.brave.com/search?q=1000002&source=web

II. Time-based history cleanup
You may use what you have left from test (I), or you join two devices to the sync chain, enable history, and do some browsing.

1. open Clear browsing data dialog, brave://settings/clearBrowserData .
2. On deviceA choose only Browsing history and Time range Last hour, press Clear data
3. Ensure corresponding history entries were deleted on other devices.

III. Ensure url from chrome.history.deleteUrl is not leaked. This is test plan for developers or for security engineers, imho QA engineers may not go over the steps below

1. Run browser with command line ./brave --enable-logging=stderr --v=0 --vmodule=commit.cc=3,*/sync/engine/*=3,traffic_logger=1 from terminal;
2. Enable/join sync chain, enable history;
3. Open page brave://inspect/#extensions
4. Click inspect under Brave extension
5. Paste at console

chrome.history.deleteUrl({url: 'https://developer.chrome.com/docs/extensions/reference/history/#method-search'}, function() {console.log("deleted");})

6. search for "url_directive": { in terminal.
   Expected not to find such records.

IV. Android

1. Join Android device to chain, enable history datatype;
2. Expected to sync History between Android device and other devices in chain.

[AlexeyBarabash]

Removed CI/Skip to get some installers for draft PR