fix: confirm page header should show address in fullscreen

[shanejonas]

Fixes: #9920

Explanation:
This PR fixes a regression in logic where it was previously using a renderTop function to decide on rendering the page headers, and always rendering children. This PR brings back that functionality of always rendering the children, instead of returning null in some cases.

Manual testing steps:

1. Use the metamask test-dapp to create a token
2. Use metamask in fullscreen
3. Send a token to any address
4. Confirm page is missing the sender to recipient addresses

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[shanejonas]

I have read the CLA Document and I hereby sign the CLA

[metamaskbot]

Builds ready [369b2ed]

• builds: chrome, firefox, opera
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• code coverage: Report
• storybook: Storybook
• all artifacts

Page Load Metrics (581 ± 9 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	43	77	57	9	4
		domContentLoaded	535	618	579	19	9
		load	537	619	581	19	9
		domInteractive	535	617	579	19	9

[danjm]

This solution looks good! Code is correct and great unit test addition. I have QA'd this in the browser.

A note for posterity (that does not need to be addressed in this PR). If we trace down the source of the logic, it looks like the showEdit prop is false if either of two conditions are met. Either (A) the confirmation is for a token approval or contract deployment, or (B) it is for a transaction which has a lastGasPrice on its local txMeta data. I think (B) can never be true while on a the confirmation screen. This possibility was eliminated long ago when we moved from the old retryTransaction method to the distinct speed up and cancel transaction methods and we handled them through UIs other than this page. A task for a different PR is to remove logic related to that case (see isTxReprice in ui/app/components/pages/confirm-transaction-base/confirm-transaction-base.component.js). I'll also note that token approval and contract deployment continue to behave correctly.