Implement publisher list v4

[zenparsing]

Resolves brave/brave-browser#9502

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:

This PR modifies how publisher status and banner information is retrieved and stored on the client. Instead of downloading the entire publisher list dataset and storing that dataset in the rewards database, we will now download a small "index" of publishers and then download publisher data for individual publishers as-needed. There should be no user-visible changes, but existing test cases that involve publisher statuses or banner data should be checked for regressions.

Basic functionality test

Flags:

--rewards=staging=true --enable-logging=stderr --v=0 --vmodule='server_publisher_fetcher=1,publisher_prefix_list_updater=1'

• Start browser with a clean profile using the flags above (additional vmodule entries can be used).
• Enable rewards.
• Dismiss the grant claim notification by clicking the small "x" in the rewards panel.
• Navigate to "https://laurenwags.github.io".
  • Verify that a "verified" check mark appears on the rewards badge.
• Open the rewards panel and click "Send a Tip".
  • Verify that the tip banner displays the correct information.

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.

[zenparsing]

• Updated rewards_database.cc so that VACUUM is not performed if transaction could not be committed.
• Updated rewards_database.cc a failed VACUUM is logged but not returned as an error to the caller.
• Updated database_server_publisher_*.cc delete methods to no-op when expired records list is empty.

[zenparsing]

CI failed due to audit_deps and an unrelated macos gclient sync failure (macos verified locally).