Placeholder to investigate Transaction Simulation and Signature Simulation UI abstraction

**What is this about?**

It seems we are maintaining separate UI styles for transaction simulation and signature simulation. We may be able to abstract some of the presentation components. This includes investigating signature simulation NativeValueDisplay and signature simulation ValueDisplay UI abstraction. Needs investigation.

Following this, we may want to investigate this in extension as well.

**Stakeholder review needed before the work gets merged**

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

Begin by locating the transaction simulation UI, signature simulation NativeValueDisplay, and signature simulation ValueDisplay components named in the issue. Compare their presentation responsibilities and determine whether a shared abstraction is practical, including the possible extension follow-up; document the investigation outcome and proposed scope before implementation.

Written by the indexing model from the issue text.