Adds recovery path for may payout problem

[NejcZdovc]

Resolves brave/brave-browser#9684

You can find diagram of what we do here https://github.com/brave/rewards/blob/master/monodraw/may_ads_payout_recovery.svg

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:

• start browser from the master
• enable rewards
• fetch promotions
• claim promotion
• make sure that promotion was claimed
• close the browser
• open db and clear unblinded_tokens table. Change change status of promotion to 1 and creds_batch status to 3. Set [] for public_keys in promotion table
• start browser from this PR
• make sure that balance is now displayed correctly

plan 2:

• start browser from the master
• enable rewards
• fetch promotions
• claim promotion
• make sure that promotion was claimed
• close the browser
• open db and change status of promotion to 1 and creds_batch status to 3. Override signed_creds value with blinded_creds value.
• start browser from this PR
• make sure that in the logs you see post out to /promotions/reportclobberedclaims
• open db and check that promotion has status 6 and creds_batch has status 5

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]

we can just update this to 2 as we do the same thing that we do with version 1 and more

[emerick]

LGTM

[NejcZdovc]

CI was aborted on windows, restarting

[kjozwiak]

Verification PASSED on macOS 10.15.4 x64 Catalina using the following build:

Brave | 1.10.48 Chromium: 81.0.4044.138 (Official Build) nightly (64-bit)
-- | --
Revision | 8c6c7ba89cc9453625af54f11fd83179e23450fa-refs/branch-heads/4044@{#999}
OS | macOS Version 10.15.4 (Build 19E287)

Case #1 (x2)

• launched 1.10.46 CR: 81.0.4044.138 using --args --log-level=2 --enable-logging=stderr --rewards=staging=true
• accepted the UGP promotion after enabling rewards via the panel and closed the browser
• opened publisher_info_db using DB Browser for SQLite
• removed all the entries under the unblinded_tokens table
• changed public_keys to [] under the promotion table
• changed status to 1 under the promotion table
• changed status to 3 under the creds_batch table
• save publisher_info_db (write changes) and exit DB Browser for SQLite
• launched 1.10.46 CR: 81.0.4044.138 using --args --log-level=2 --enable-logging=stderr --rewards=staging=true and you'll notice that the balance displays 0.00 BAT
• launch 1.10.48 CR: 81.0.4044.138 using --args --log-level=2 --enable-logging=stderr --rewards=staging=true and you'll notice that the balance displays 20.00 BAT
• tip https://laurenwags.github.io, https://duckduckgo.com

Before removing the "unblinded_tokens" table

After removing the "unblinded_tokens" table

Changing "promotion" table

Changing "creds_batch" table

Broken state after the above changes

Case #2 (x2)

• launched 1.10.46 CR: 81.0.4044.138 using --args --log-level=2 --enable-logging=stderr --rewards=staging=true
• accepted the UGP promotion after enabling rewards via the panel and closed the browser
• opened publisher_info_db using DB Browser for SQLite
• changed status to 1 under the promotion table
• changed status to 3 under the creds_batch table
• replace signed_creds with blinded_creds in the creds_batch table
• save publisher_info_db (write changes) and exit DB Browser for SQLite
• launch 1.10.48 CR: 81.0.4044.138 using --args --log-level=2 --enable-logging=stderr --rewards=staging=true

[ REQUEST ]
> url: https://grant.rewards.bravesoftware.com/v2/promotions/reportclobberedclaims
> method: UrlMethod::POST
> content: {"claimIds":["29ab8b87-45f8-47c3-a684-d0cd253b8547"]}
> contentType: application/json; charset=utf-8
[ END REQUEST ]

• opened publisher_info_db using DB Browser for SQLite
• ensure that the status under promotion is 6
• ensure that the status under creds_batch is 5

Changing "status" under the "promotion" table

Changing "status" and "signed_creds" under the "creds_batch" table

"status" under the "promotion" table after upgrading

"status" under the "creds_batch" table after upgrading