feat(simulation): add transaction inspector timeline

[Marvellous805]

Summary

• add a reusable, typed transaction simulation timeline component
• surface policy and insufficient-fee failures with actionable remediation and expandable payload diagnostics
• visualize network, resource, and refundable fee estimates with Recharts
• include success and policy-rejection mock payloads for proposal-review integration

Closes #75

Validation

• reviewed the branch diff and confirmed strict TypeScript-safe data contracts (no �ny)
• local
  pm run build could not run because the workspace drive is full (ENOSPC), preventing dependency installation

[vercel]

@Marvellous805 is attempting to deploy a commit to the Cjay's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@Marvellous805 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[mergekeeper]

MergeKeeper review

Scope: in scope for linked issue #75.
Verdict: clean

The PR successfully implements the transaction simulation timeline and failure diagnosis component matching all requirements and acceptance criteria.

Reviewed commit: 42d3b75ce18847bd662890b8896b37f958c9b40f.
CI and merge eligibility are checked separately.

[mergekeeper]

Approved

The PR successfully implements the transaction simulation timeline and failure diagnosis component matching all requirements and acceptance criteria.

[mergekeeper]

MergeKeeper merge status

Status: blocked
PR state: open
Mergeability: mergeable
Checked commit: 42d3b75ce18847bd662890b8896b37f958c9b40f.

Reason:
GitHub pull request merge request failed with 405: 3 of 3 required status checks are expected.

Next steps:
This required status check is enforced directly by the repository's branch rules, independent of MergeKeeper's own CI evaluation — a maintainer merge override cannot bypass it unless MergeKeeper is authorized to.

1. Wait for the check to pass, or fix the underlying failure.
2. To let an explicit override bypass this check going forward, add the MergeKeeper GitHub App as a Bypass actor on the ruleset (Settings → Rules → Rulesets → the ruleset → Bypass list).