[Android] Fix for safe browsing

[samartnik]

This is temporary fix to keep using safetynet for checking urls for safe browsing. We will have to change the way we handle it in C130 due to this change https://source.chromium.org/chromium/chromium/src/+/e5700c49b75254cc1201a3bbea59b20b06328a27

Resolves brave/brave-browser#41060

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• 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 wiki
  • npm run presubmit wiki, 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/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

[github-actions]

The security team is monitoring all repositories for certain keywords. This PR includes the word(s) "safe browsing" and so security team members have been added as reviewers to take a look.

No need to request a full security review at this stage, the security team will take a look shortly and either clear the label or request more information/changes.

Notifications have already been sent, but if this is blocking your merge feel free to reach out directly to the security team on Slack so that we can expedite this check.

[SergeyZhukovsky]

++

[kjozwiak]

Verification PASSED on Pixel 6 running Android 15 using the following build(s):

Brave | 1.72.13 Chromium: 129.0.6668.42 (Official Build) canary (64-bit)
--- | ---
Revision | d12479197db15ec73436d23bea8724b01103ef15
OS | Android 15; Build/AP41.240726.010; 35; REL

Using the STR/Cases brave/brave-browser#41060 (comment), ensured that the Safe Browsing was working as expected as per the following:

Webpage Warnings - phishing warning

• ensured that the phishing warning is being displayed correctly
• ensured that you can proceed past the warning without any issues

Example	Example

Webpage Warnings - malware warning

• ensured that the malware warning is being displayed correctly
• ensured that you can proceed past the warning without any issues

Example	Example

Webpage Warnings - unwanted software warning

• ensured that the unwanted software warning is being displayed correctly
• ensured that you can proceed past the warning without any issues

Example	Example

Webpage Warnings - billing warning

• ensured that the billing warning is being displayed correctly
• ensured that you can proceed past the warning without any issues

Example	Example

Mobile Download Warnings - harmful file

• ensured that the harmful file modal is being displayed correctly
• ensured that you can proceed past the warning and download the file without any issues