Handles better failure cases on Android Safe Browsing

[SergeyZhukovsky]

Resolves brave/brave-browser#31894

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 lint, 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/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:

[samartnik]

lgtm

[AlexeyBarabash]

++

[deeppandya]

LGTM

[fmarier]

Looks good to me, but I think we might want to restrict Safe Browsing checks to just HTTP and HTTPS too (maybe in a separate PR).

[fmarier]

Is DEFAULT_CHECK_DELTA in seconds?

[SergeyZhukovsky]

// |check_delta| is the number of microseconds it took to look up the URL
// reputation from GmsCore.

[SergeyZhukovsky]

Looks good to me, but I think we might want to restrict Safe Browsing checks to just HTTP and HTTPS too (maybe in a separate PR).

sounds good, I'll create a follow up

[kjozwiak]

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

Brave | 1.58.66 Chromium: 116.0.5845.51 (Official Build) canary (64-bit)
--- | ---
Revision | 760f994002820ae85421061cfac48e987a605c03
OS | Android 14; Build/UPB4.230623.007; 34; REL

Using the STR/Cases outlined via brave/brave-browser#31894 (comment), reproduced that FB was initially loading slowly as per the following:

screen-20230802-223929.mp4

Ensured that the page was loading quicker/shorter delay with 1.58.66 Chromium: 116.0.5845.51 as per the following:

screen-20230803-020734.mp4