Fix a bug where non-address types would be rendered as addresses in EIP-712

[FrederikBolding]

Explanation

Adds type annotation to sanitized EIP-712 messages such that the type annotation can be used for selecting how to display data.

This also fixes #17711

[metamaskbot]

Builds ready [4688a99]

• builds: chrome, firefox
• builds (beta): chrome, firefox
• builds (flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4
  • common: 0, 1, 2, 3, 4, 5
  • content-script: 0
  • contentscript: contentscript
  • disable-console: disable-console
  • inpage: inpage
  • policy-load: policy-load
  • sentry-install: sentry-install
  • ui: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1813 ± 83 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	103	318	143	45	21
		domContentLoaded	1478	2147	1763	156	75
		load	1478	2147	1813	173	83
		domInteractive	1478	2147	1763	156	75

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 0 bytes
• ui: 36 bytes
• common: 43 bytes

[jpuri]

Hey are test cases below no longer relevant ?

[FrederikBolding]

They were seemingly misunderstandings of what data the component should show, so I removed them because they would fail now that I changed the component input to be valid too 😅