Use new Rust based ad-block library

[bbondy]

Fix brave/brave-browser#4793
Please let me merge if approved, I still need to verify CI.

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
  • Windows
  • macOS
  • Linux
• Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests && npm run test-security) on
  • Windows
  • macOS
  • Linux
• 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:

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, had a couple of minor typo nits

[mkarolin]

No successful CI build yet (and I can't build locally on mac at the moment) so I am not sure where libadblock ends up and if the signing script needs to be patched to have it signed.

[bbondy]

(and I can't build locally on mac at the moment)

Do you mean you can't build this PR in particular? Or you can't build at all?

if the signing script needs to be patched to have it signed.

There's a commit to do the signing of it already. I haven't verified on CI if that works yet though.

[mkarolin]

(and I can't build locally on mac at the moment)

Do you mean you can't build this PR in particular? Or you can't build at all?

Just meant I was on Windows and couldn't switch to Mac at that moment.

[simonhong]

There's a commit to do the signing of it already. I haven't verified on CI if that works yet though.

@bbondy I think you missed one thing in that commit.
See https://github.com/brave/brave-core/blob/master/patches/chrome-installer-mac-signing-signing.py.patch#L26 cc:@mkarolin