Updates Open in Tor view in location bar.

[mkarolin]

Resolves brave/brave-browser#39383

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:

[mkarolin]

@simonhong, I think putting this action on the left of all others (as @aguscruiz proposed in brave/brave-browser#39383 (comment)) might be a bit complicated so I was thinking of leaving that out as a follow up. If you can think of an easy implementation for that, please, let me know.

[simonhong]

@simonhong, I think putting this action on the left of all others (as @aguscruiz proposed in brave/brave-browser#39383 (comment)) might be a bit complicated so I was thinking of leaving that out as a follow up. If you can think of an easy implementation for that, please, let me know.

Tried to set it to left most of trailing view. WDYT?

[mkarolin]

Tried to set it to left most of trailing view. WDYT?

Thanks @simonhong, I think that looks great. 😻

I added one little simplification in 2521f39

[simonhong]

++

[bsclifton]

string reviewers ++ 😄👍

[GeetaSarvadnya]

Verification INPROGRESS on

Brave | 1.69.90 Chromium: 127.0.6533.26 (Official Build) nightly (64-bit)
-- | --
Revision | f28a94aea02a03674fe24a352cb52453b6132be2
OS | Windows 10 Version 22H2 (Build 19045.4529)

Verified the comments from #24447 (comment)
Confirmed that Open in Tor button is updated as per the design on the bave.com and mail.protonmail.com

Example	Example

[GeetaSarvadnya]

@mkarolin @simonhong: @rebron wants to retain logo only not text as per the slack communication https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1720472348031839?thread_ts=1720455221.114959&cid=CHGKGMHDJ

[simonhong]

@mkarolin @simonhong: @rebron wants to retain logo only not text as per the slack communication https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1720472348031839?thread_ts=1720455221.114959&cid=CHGKGMHDJ

@mkarolin pushed PR for it - #24561