Fix Include in Auto-Contribute toggle

[emerick]

Resolves brave/brave-browser#14413

Internally, we store the publisher exclusion state as an integer-based enumeration. However, some of our publisher-related extension API functions send this value as a boolean while others send it as a number. This was causing confusion in the UI as any non-zero number was causing the state to be interpreted as excluded.

Since we only use this state as a Boolean in the UI (i.e., nothing in the UI cares about anything other than two states: exclude or include), I standardized on always sending it to the UI as a Boolean.

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:

• Visit https://twitter.com/bravelaurenwags
• Open Rewards panel a few times and verify that toggle state of "Include in Auto-Contribution" doesn't change
• Toggle the state of the button
• Open Rewards panel a few times and verify that toggle state of "Include in Auto-Contribution" doesn't change

I'd repeat these steps a few times and also try with a clean profile. There are also useful STR in brave/brave-browser#14413 that we should also check.

[zenparsing]

This is great - eventually we'll get rid of all of these C++ enum values leaking into JS!

[emerick]

Android, Linux, Windows passed CI; restarting for Mac and iOS.

[emerick]

CI passed on iOS and MacOS, ready to merge.