Show domain info when signing messages

[supermassive]

Resolves brave/brave-browser#28048

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• 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:

Sing message ui should show domain field content for v3 and v4 signature types

Desktop: #16935 (comment)
Android:

[onyb]

This what the panel looks like after my UI updates in b3cf58e.

Personal Sign	Sign Typed Data V3	Sign Typed Data V4	Sign Typed Data V4 (⚠️)

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[Douglashdaniel]

++ Front-end

[yrliou]

Added @SergeyZhukovsky as a reviewer for Android commit.

[SergeyZhukovsky]

please add translateable="false" for both strings as nothing to translate there.

[SergeyZhukovsky]

please address the small comment I left for Android. Otherwise Android part ++

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[srirambv]

Verification passed on

Brave	1.50.3 Chromium: 110.0.5481.52 (Official Build) nightly (64-bit)
Revision	979113183ded4544a2c443aceb1629c430907e52-refs/branch-heads/5481@{#636}
OS	Linux

• Verified domain info is shown on signing messages for v3/v4 messages

Personal Sign	Sign Type V3	Sign Type V4

---

Verification passed on Oppo Reno 5 with Android 13 running 1.50.3 x64 Nightly build

• Verified domain info is shown on signing messages for v3/v4 messages

16935.mp4