Fixes browser doesn't retry to get signed tokens in all cases

[tmancey]

Fixes brave/brave-browser#6647
Requires: #4146

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

See brave/brave-browser#6647

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.

[tmancey]

Unrelated CI issue with components_strings.grd

[tmancey]

@kjozwiak @LaurenWags

You'll need to run through the following when retrieving the {payment_id}:

• launch brave and enable rewards via brave://rewards
• once enabled, disable ads via brave://rewards
• retrieve the {payment_id} via brave://rewards-internals or any other method
• close the browser and remove Default/rewards_service/confirmations.json
• launch the browser and ensure that Charles Proxy is setup correctly as mentioned below

Cases:

Launch the browser with logging to the console log and wait for OnRequestSignedTokens to fail (Search for this in the console log), then disable the rewrite and make sure that Confirmations retries and successfully requests the signed tokens.

Following the same steps as below, add a rewrite rule for /v1/confirmation/token/{payment_id}?nonce=* where {payment_id} has been replaced with your payment id and replacing match code from 201 to 200 HTTP_OK.

Setting up Charles Proxy:

• Navigate to Tools > Rewrite
• Click the "Add" button
• Confirm "Enable Rewrite" is checked
• Tap the "Add" button:

- I would recommend editing the name to reflect the ticket number (as you can export and keep these tests for future use):

- Tap the "Add" button:

- Enter the following information (replacing `{payment_id}` with your payment id, and changing "Host" for other environments such as staging):

- Tap the "OK" button - Tap the "Add" button

- Enter the following formation:

- Tap the "OK" button - Tap the "Apply" button:

- Tap the "OK" button