Add configurable default tip amounts

[jhoneycutt]

Submitter Checklist:

Resolves brave/brave-browser#6011

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

Test case

1. Launch on staging
2. Enable Rewards and claim grant
3. Visit a verified publisher with publisher-defined default tip amounts
4. Open tip panel and choose "Send a tip..."
5. Ensure that publisher's defaults are shown in the site banner

Test case

1. Launch on staging
2. Enable Rewards and claim grant
3. Visit a publisher without publisher-defined default tip amounts
4. Open tip panel and choose "Send a tip..."
5. Ensure that wallet's defaults of [1, 10, 50] BAT are shown in the site banner

Test case

1. Launch on staging
2. Enable Rewards and claim grant
3. Visit a publisher with publisher-defined default tip amounts
4. Open tip panel and choose "Set..." to set a monthly contribution
5. Ensure that publisher's defaults are shown in the site banner

Test case

1. Launch on staging
2. Enable Rewards and claim grant
3. Visit a publisher without publisher-defined default tip amounts
4. Open tip panel and choose "Set..." to set a monthly contribution
5. Ensure that wallet's defaults of [1, 10, 50] BAT are shown in the site banner

Test case

1. Launch on staging
2. Enable Rewards and claim grant
3. Visit a publisher with publisher-defined default tip amounts
4. Open tip panel and choose "Set..." to set a monthly contribution
5. Set monthly contribution to any value and click "Set Contribution"
6. Open tip panel again
7. Ensure that "Monthly Contribution" shows the value from step 4
8. Click the value to change it
9. Ensure that publisher's defaults are shown in the menu

Test case

1. Launch on staging
2. Enable Rewards and claim grant
3. Visit a publisher without publisher-defined default tip amounts
4. Open tip panel and choose "Set..." to set a monthly contribution
5. Set contribution to 1.0 BAT and click "Set Contribution"
6. Open tip panel again
7. Ensure that "Monthly Contribution" shows "1.0 BAT"
8. Click the value to change it
9. Ensure that wallet's defaults of [1, 10, 50] BAT are shown in the menu

Test case

1. Launch on staging
2. Enable Rewards and claim grant
3. Visit a publisher with publisher-defined default tip amounts
4. Open tip panel and choose "Set..." to set a monthly contribution
5. Set monthly contribution to any value and click "Set Contribution"
6. Close the browser tab
7. Modify values in server_publisher_amounts table in publisher_info_db to change the value set in step 4 to another value. For example, if the publisher has defaults of [5, 10, 20], and you selected 5 BAT in step 4, change the value in the table from 5 to 6 BAT
8. Open a new tab with the same publisher
9. Open tip panel again
10. Ensure that "Monthly Contribution" shows the value from step 3
11. Click the value to change it
12. Ensure that publisher's new defaults are shown in the menu (e.g. [6, 10, 20])

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.

[jhoneycutt]

Failed pipeline steps are the network audit test, which appears to be filed as brave/brave-browser#6189.

[ryanml]

Can you confirm that we don't need a migration path on upgrade for new wallet properties? (For the client side, in case the now non-optional default tip choices wallet property is not immediately present)

[jhoneycutt]

Can you confirm that we don't need a migration path on upgrade for new wallet properties? (For the client side, in case the now non-optional default tip choices wallet property is not immediately present)

We do not, and I've just added a unit test for this.

[tmancey]

prefix(optional) R "delimiter( raw_characters )delimiter" (6) (since C++11)

[NejcZdovc]

Preselected amount is not working. So when you open tip banner, middle selections should be preselected. In this PR this doesn't happen anymore. Same thing needs to happen on monthly tip.

Expected:

Actual:

[jhoneycutt]

Issue with default not being pre-selected noticed by @NejcZdovc was fixed.

[mandar-brave]

@jhoneycutt @NejcZdovc can we unblock the merge and get in to Master?

[kjozwiak]

Went through the STR/Cases outlined under #3848 (comment) under the following build:

Brave	1.5.15 Chromium: 79.0.3945.88 (Official Build) nightly (64-bit)
Revision	c2a58a36b9411c80829b4b154bfcab97e581f1f3-refs/branch-heads/3945@{#954}
OS	macOS Version 10.15.2 (Build 19C57)

Looks like everything is working as expected 👍 Going to start the uplift process for #4248.