Improve contrast for pinned tabs outline

[aguscruiz]

Resolves brave/brave-browser#41720

Current pinned tabs outline color:

New pinned tabs outline color:

---

Current active state for tabs (release):

New active state for tabs:

---

Current active state for tabs (release - not visible):

New hover state for tabs:

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:

[fallaciousreasoning]

lgtm

[github-actions]

[puLL-Merge] - brave/brave-core@26213

Description

This PR makes several changes across the codebase, primarily focused on implementing a new creator detection feature for Brave Rewards, updating various components, and making improvements to the search functionality on the New Tab Page. The changes also include some security improvements and bug fixes.

Possible Issues

1. The removal of Greaselion-related code might affect existing functionality that depends on it.
2. The changes to the Tor client updater and launcher might introduce new edge cases or security considerations.
3. The new creator detection feature might have performance implications on certain websites.

Security Hotspots

1. Changes to the Tor client updater and launcher (components/tor/) should be carefully reviewed for potential security implications.
2. Modifications to the Safe Browsing API handler (components/safe_browsing/) need to be scrutinized for any potential weaknesses in threat detection.

Changes

Changes

1. browser/brave_rewards/:

   • Implemented a new creator detection feature for media platforms.
   • Removed Greaselion-related code and dependencies.
   • Updated reward service to use the new creator detection mechanism.

2. components/brave_rewards/:

   • Added new files for creator detection scripts.
   • Updated publisher utils to support the new creator detection feature.

3. components/tor/:

   • Refactored the Tor client updater and launcher.
   • Added new constants and utility functions for Tor paths.

4. components/safe_browsing/:

   • Updated the Safe Browsing API handler to support multiple threats.
   • Implemented a priority system for handling multiple threats.

5. brave-ios/:

   • Made improvements to URL display and handling in various parts of the iOS app.
   • Updated the bookmarks and history views.

6. New Tab Page:

   • Implemented a new search engine context provider.
   • Updated the search box functionality on the New Tab Page.

7. Various other updates and improvements across the codebase, including version bumps and minor bug fixes.

8. Updated test files and performance profiles.

Overall, this PR represents a significant update to the Brave browser, with a focus on improving the Rewards system, search functionality, and security features.