[iOS] - Properly handle URL eliding when blobs are given.

[Brandon-T]

Summary

• On line 100 of the file below, it has a check for url.SchemeIsBlob(), and if it is, ALL url parsers fail to parse the host (Swift Foundation URL, GURL, NSURL, etc). The URL ends up having no host or path!
• So we explicitly do the same by checking if the scheme is blob. If it is, then we use URLOrigin to parse the host and use that as the URL to be formatted. Safari does the same.
• Note: On Chrome Desktop (and Brave Desktop), this is broken as well!
• Source: https://source.chromium.org/chromium/chromium/src/+/main:components/omnibox/browser/location_bar_model_impl.cc;l=100;drc=04989307509c78d67b34f2282ca549397719d046?q=components%2Fomnibox%2Fbrowser%2Flocation_bar_model_impl.cc&ss=chromium%2Fchromium%2Fsrc

Resolves brave/brave-browser#41716
Resolves https://github.com/brave/internal/issues/1210

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) "url parse" 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.

[stoletheminerals]

Note: On Chrome Desktop (and Brave Desktop), this is broken as well!

Are you sure? I can't reproduce it on Desktop or Android

[brave-builds]

Released in v1.73.26

[Uni-verse]

Verified on iPhone 12 running iOS 18.0 using version 1.73 (27)

• Verified STR/test cases mentioned in [iOS] - Properly handle URL eliding when blobs are given. #26085 (comment) and https://hackerone.com/reports/2790405

1.72.x	1.73.27