Fixes sku contribution flow for unblinded tokens

[NejcZdovc]

Resolves brave/brave-browser#9962

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:

plan 1:

• enable rewards
• add verified publisher to AC list
• connect KYC uphold wallet
• wait for AC to trigger
• make sure that contribution goes through

plan 2:

• enable rewards
• claim grant
• tip one verified publisher
• make sure that tip goes through

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.

[NejcZdovc]

for this two processors we need to go through different credentials flow as for brave funds

[emerick]

LGTM

[LaurenWags]

@NejcZdovc I'm still seeing the issue @GeetaSarvadnya described in brave/brave-browser#9962. Here are the STR I used:

plan 1 from above description:

Attempt 1:
enable rewards
add verified publisher to AC list (used DDG on staging which is a connected publisher)
connect KYC uphold wallet
wait for AC to trigger
--> AC does not go through

Attempt 2:
after above AC failed (on same profile), added a new verified publisher to AC list (used 3zsistemi.si on staging which is a KYC'd publisher)
wait for AC to trigger
--> AC does not go through

In both attempt 1 & 2 I get this:

Seems as though AC is not working for me on Nightly with an Uphold wallet.

Brave | 1.11.37 Chromium: 83.0.4103.61 (Official Build) nightly (64-bit)
-- | --
Revision | 94f915a8d7c408b09cc7352161ad592299f384d2-refs/branch-heads/4103@{#561}
OS | macOS Version 10.14.6 (Build 18G3020)

Update - upon further inspection there seems to be a server side issue with staging env.

[LaurenWags]

Verified passed with

Brave | 1.11.37 Chromium: 83.0.4103.61 (Official Build) nightly (64-bit)
-- | --
Revision | 94f915a8d7c408b09cc7352161ad592299f384d2-refs/branch-heads/4103@{#561}
OS | macOS Version 10.14.6 (Build 18G3020)

• Verified test plan from #5671 (comment) using development env as per #5671 (comment) there is an issue with the staging server at this time.

Plan 1:

1. enable rewards (dev env)
2. add verified publisher to AC list
3. connect KYC uphold wallet
4. wait for AC to trigger
5. make sure that contribution goes through

Plan 2:

1. enable rewards (dev env)
2. claim grant
3. tip one verified publisher
4. make sure that tip goes through