Applied Shields v2 UX to settings and shields panel and use FP V2 by default

[simonhong]

Resolves brave/brave-browser#9194
Resolves brave/brave-browser#9975

---

---

---

---

---

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Android
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that these changes pass automated tests (unit, browser, security tests) on
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that all lint errors/warnings are resolved (npm run lint)
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone
• Public documentation has been updated as necessary. 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-issues-with-tracking-protection
  • https://github.com/brave/brave-browser/wiki/QA-Guide

Test Plan:

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

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.

[simonhong]

@pes10k @rebron I think this PR is ready to review :)

[rebron]

Labels and renaming looks great. Will leave the rest to @pes10k.

[pes10k]

Fantastic!

[pes10k]

This all looks great to me, terrific @simonhong !

[simonhong]

@bridiver ping to owners review.

[bridiver]

doesn't this also need a v2 check?

[simonhong]

In the UI, same string default is only used for BLOCK_THIRD_PARTY and DEFAULT.

[simonhong]

@rebron I'll revisit and update this PR again after fingerprint v2 is enabled by default.
@bridiver told me that these new option names are valid only for v2. cc: @pes10k

[pes10k]

Yep, these are for v2 fingerprinting, but we're aiming to ship v2 in 1.11, so should all line up :)

Right now the v2 fingerprinting protects haven't been fully implemented, but have eclipsed what was available in v1, so switching over to v2, even as is, is strictly superior

[bridiver]

this is not relevant anymore, there is no longer a first/third party scope. Can you please cleanup the tests in a followup?

[simonhong]

brave/brave-browser#10078