Add per-site farbling token support

[goodov]

Changes in this PR:

• Add a WebsiteSetting BraveShieldsMetadata bound to the Schemeful site (eTLD+1).
• Generate and store farbling token as base::Token in this setting for each site.
• Pass the token as a part of ShieldsSettings mojo struct to renderer.
• Support the setting cleanup as a part of DATA_TYPE_COOKIES or DATA_TYPE_HISTORY cleanup
• Support cleanup via the site data cleanup settings page. The metadata is not included in the size calculation, but if any other data exists and is requested to be deleted, shields metadata will also be nuked.

Resolves https://github.com/brave/brave-browser/issues/28904

Submitter Checklist:

• [x] I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• [x] There is a ticket for my issue
• [x] Used Github auto-closing keywords in the PR description above
• [x] 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: