New Tab Page WebUI - remove widget visibility migration

[petemill]

Resolves brave/brave-browser#20501

The migration was also checking for whether the user had previously connected to a widget by requesting data, instead of checking the token.

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:

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[wknapik]

@petemill I just added the CI/run-network-audit label. You might want to rebuild.

[simonhong]

++

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[kjozwiak]

Verification PASSED on Win 11 x64 using the following build:

Brave | 1.36.48 Chromium: 97.0.4692.71 (Official Build) nightly (64-bit)
-- | --
Revision | adefa7837d02a07a604c1e6eff0b3a09422ab88d-refs/branch-heads/4692@{#1247}
OS | Windows 11 Version 21H2 (Build 22000.434)

Clean Install Cases

Verified the STR/Cases outlined via brave/brave-browser#20501 (comment) and ensured that there wasn't any outbound network connections when opening the NTP on a new profile. Example:

Also ensured that none of the crypto widgets were visible on a new profile but were available via the following:

• Customise dashboard -> Cards

Upgrade Cases

For the following cases, upgrade from 1.36.47 Chromium: 97.0.4692.71 --> 1.36.48 Chromium: 97.0.4692.71

• ensured that crypto widgets are being displayed in the widget stack if a user has already enabled them
  • checked using Binance, FTX & Gemini
• ensured that users stay authenticated after upgrading when the widget is active/visible under the widget stack
• ensured that users stay authenticated after upgrading when the authenticated widget isn't active/visible in the widget stack
• ensured that the correct order/active widget is maintained after upgrading
• ensured that crypto widgets are not being removed from the widget stack and into Customise dashboard -> Cards when they've been enabled