Adds pagination to publisher list

[NejcZdovc]

Resolves brave/brave-browser#9607

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:

• make sure that list downloads and verified publisher show up (Test it on staging)

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.

[emerick]

LGTM, just had one comment

[LaurenWags]

Verified passed with

Brave | 1.10.39 Chromium: 81.0.4044.138 (Official Build) nightly (64-bit)
-- | --
Revision | 8c6c7ba89cc9453625af54f11fd83179e23450fa-refs/branch-heads/4044@{#999}
OS | macOS Version 10.14.6 (Build 18G3020)

• Verified test plan from Adds pagination to publisher list #5458 (comment)

• Confirmed verified, KYC'd publishers show as verified on staging:

• Confirmed display of custom tip banner for both one time and monthly tips:

• Confirmed if I connect a KYC'd user wallet, I am able to see connected, but not KYC'd publishers as verified w/ proper messaging on panel and tip banners:

• Confirmed able to see verified websites, YouTube channels above and confirmed able to see verified Twitch, GitHub, Reddit, Vimeo, and Twitter pages also.

[LaurenWags]

Verified passed with

Brave | 1.10.39 Chromium: 81.0.4044.138 (Official Build) canary (32-bit)
-- | --
Revision | 8c6c7ba89cc9453625af54f11fd83179e23450fa-refs/branch-heads/4044@{#999}
OS | Android 10; Pixel 3 XL Build/QQ2A.200305.002

• Confirmed able to see the following verified publisher types on Android: regular sites, youtube channels, twitter, vimeo, and github. See notes below about twitch, reddit.
  
  
  
  
  

• Note, custom banners do not display on Android. This is a known issue logged previously with custom tipping banners not displayed  brave-browser#7766

• Note, Twitch publishers do not show as verified on Android. This is a known issue logged previously with [Android] Verified Twitch account doesn't show verified in BR panel brave-browser#7826

• Note, Reddit publishers do not show on Android, logged [Android] Reddit publishers are not recognized on Android brave-browser#9698

• Logged the following issues while testing, but they are not related to this PR:

  • [Android] Github publishers do not show 'on GitHub' on Rewards panel brave-browser#9696
  • [Android] panel on Android uses 'publisher' but should probably say 'creator' brave-browser#9697