Fix phantom de-amp toggle

[ShivanKaul]

Resolves brave/brave-browser#21788

Put de-amp setting in brave personalization options.

Screenshots:

(new setting placement)

(no phantom toggle button)

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:

[petemill]

As discussed, we can avoid this template patch / modification entirely by instead placing the amp settings-toggle-button at https://github.com/brave/brave-core/blob/master/browser/resources/settings/brave_privacy_page/brave_personalization_options.html#L56

[ShivanKaul]

There's an open issue for the one test failure on Windows: brave/brave-browser#21809, Slack discussion.

[kjozwiak]

Removing the 1.38.x milestone as this hasn't been completed/merged. At this point, master is on 1.39.x so this will be going into 1.39.x. As per brave/brave-browser#21788 (comment), we'll need to get an uplifted created for 1.38.x.

[petemill]

Great cleanup! Please squash away the other commit before merge.

[petemill]

remove extra whitespace

[kjozwiak]

Verification PASSED on Win 11 x64 using the following build(s):

Brave | 1.39.2 Chromium: 100.0.4896.46 (Official Build) nightly (64-bit)
-- | --
Revision | 5ca33821b2211805855c77d334353d27c616a7ca-refs/branch-heads/4896@{#584}
OS | Windows 11 Version 21H2 (Build 22000.556)

Verified the STR/Cases outline via https://github.com/brave/brave-browser/issues/21788#issue-1175088211%20&%20https://github.com/brave/brave-browser/issues/21788#issuecomment-1074781639. Also ensured that:

• enabling/disabling Auto-redirect AMP pages doesn't display any rogue toggles.

Example	Example	Example	Example