Fix stringified object on NFT approve screen

[FrederikBolding]

Explanation

Fixes a stringified object on the NFT approve screen. Since the title is a React object and not a string in case of "unknown NFTs" we need to render it as a React object instead of a string.

Screenshots/Screencaps

Before

After

Manual Testing Steps

1. Go to https://etherscan.io/address/0x1e52F7A450b08b1B249A4f4f54518fC5278C2285#writeContract
2. Create a "setApprovalForAll" transaction to any address
3. See that no stringified objects are present on the screen

Pre-Merge Checklist

• PR template is filled out
• IF this PR fixes a bug, a test that would have caught the bug has been added
• PR is linked to the appropriate GitHub issue
• PR has been added to the appropriate release Milestone

+ If there are functional changes:

• Manual testing complete & passed
• "Extension QA Board" label has been applied

[adonesky1]

👍

[metamaskbot]

Builds ready [f5d86b7]

• builds: chrome, firefox, opera
• builds (beta): chrome, firefox, opera
• builds (flask): chrome, firefox, opera
• build viz: Build System
• mv3: MV3 Background Module Init Stats
• mv3: MV3 UI Init Stats
• mv3: Module Load Stats
• code coverage: Report
• storybook: Storybook
• all artifacts
• bundle viz:

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

Page Load Metrics (1930 ± 69 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	87	216	116	28	14
		domContentLoaded	1715	2157	1901	134	65
		load	1732	2272	1930	143	69
		domInteractive	1715	2157	1901	134	65

highlights:

storybook

• ui/pages/confirm-approve/confirm-approve-content/confirm-approve-content.stories.js
• ui/pages/confirm-approve/confirm-approve.stories.js