Remove semi-verified state

[szilardszaloki]

Do the linking of the Uphold account to the Brave wallet during authorization.

Added the balance fetching of the anonymous wallet to the Uphold authorization flow.
Removed fetching the balances for all the wallet types (anonymous, blinded, uphold and bitflyer) and removed linking from the generate wallet flow.

Resolves brave/brave-browser#15390.

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
• 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:

[zenparsing]

Looks good! I'll build this branch and give it a run-through tomorrow.

[bsclifton]

Definitely not something we should address with this PR, but I'm curious (@zenparsing, @emerick, @szilardszaloki) if it would make sense to switch to using constants for the info levels?

brave-core/vendor/bat-native-ledger/src/bat/ledger/internal/logging/logging.h

Lines 45 to 53 in 5a4a600

	// BAT Ledger verbose levels:
	//
	// 0 Error
	// 1 Info
	// 5 URL request
	// 6 URL response
	// 7 URL response (with large body)
	// 8 Database queries
	// 9 Detailed debugging (response headers, etc)

We could address by making an enum

enum LedgerLogLevel {
    Error,
    Info,
    UrlRequest = 5,
    UrlResponse,
    UrlResponseWithBody,
    DbQueries
};
// ...
if (wallet->payment_id.empty()) {
    BLOG(LedgerLogLevel::Error, "Payment ID is empty!");
    // ...

[szilardszaloki]

This would be a lot more informative.

[emerick]

I definitely like that idea.

[bsclifton]

Nice usage of parameterized tests! These are really cool 😄

For other reviewers, more info at https://source.chromium.org/chromium/chromium/src/+/main:third_party/googletest/src/googletest/include/gtest/gtest-param-test.h;l=71-93;drc=0a3a3a845e136a9a6ccd8e9b924b848840f22b7b

[bsclifton]

Closing as this should have been covered in #9212

cc: @szilardszaloki in case I missed something 😄