[Omnibox]: Rank bookmarks which match the user input more highly

[fallaciousreasoning]

Resolves brave/brave-browser#44374

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:

1. Bookmark a page and give the bookmark a unique name
2. Enter the exact title of the bookmark
3. It should be the default match (assuming you don't have a history entry for something very similar) and/or the name isn't very short

[simonhong]

IMO, we could adjust each match's relevance by overriding CalculateBookmarkMatchRelevance().
Then, we could avoid unnecessary full iteration of matches_. WDYT?

[fallaciousreasoning]

@simonhong we could do that but we'd still need an iteration to handle setting allowed_to_be_default_match (and fill_into_edit) because that method doesn't get passed an AutocompleteMatch.

We could still split it into two parts (and adjust the relevance in CalculateBookmarkMatchRelevance) but I think it makes sense to do both in the same place.

[simonhong]

++ 👍🏼

[brave-builds]

Released in v1.78.19