Add Shields Ad/Fingerprint block setting questions

[DJAndries]

Resolves brave/brave-browser#21345

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• 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, npm run lint, 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:

1. Start with fresh installation of browser
2. Access brave://local-state. Verify that the P3A metrics Brave.Shields.AdBlockSetting and Brave.Shields.FingerprintBlockSetting have a value of 1.
3. Change the global "Trackers & ads blocking" setting to "Aggressive". Verify that the ad block setting metric has a value of 2, on the local state page. Verify that the fingerprint block setting metric still has a value of 1.
4. Change the global "Trackers & ads blocking" setting to "Standard". Verify that the ad block setting metric has a value of 1, on the local state page.
5. Change the global "Trackers & ads blocking" setting to "Disabled". Verify that the ad block setting metric has a value of 0, on the local state page.
6. Change the global "Fingerprinting blocking" setting to "Strict". Verify that the fingerprint block setting metric has a value of 2. Verify that the ad block setting metric still has a value of 0.
7. Change the global "Fingerprinting blocking" setting to "Standard". Verify that the fingerprint block setting metric has a value of 1.
8. Change the global "Fingerprinting blocking" setting to "Disabled". Verify that the fingerprint block setting metric has a value of 0.

[iefremov]

just curious why not put it into DefaultBraveShieldsHandler::SetFingerprintingControlType ?

[DJAndries]

it seems that Android has it's own preference bridge/handler, so I thought I'd add it here so that the reporting works on all platforms