release: align pending transaction details with confirmed transactions

[moscowchill]

Summary

Release the reviewed pending transaction details alignment from dev.

• Use the same heading, neutral transaction type, theme-aware card and responsive address flow as confirmed transactions.
• Preserve explicit Pending status, elapsed time, estimated inclusion, and existing mined/dropped/unavailable behavior.
• Preserve complete address links/copy values and keep pending contract creation truthful until confirmation.

Validation

• Reviewed source PR fix(explorer): align pending transaction details #201 and the exact candidate tree.
• 639 unit tests, 47 production-build browser cases, lint, TypeScript, API drift, scoped formatting and build passed.
• Independent source review passed. Phone/desktop and both themes were checked, including pending-to-mined transitions, dropped transactions and temporary API failures.
• No backend, database, node, dependency, faucet or hosted example changes. No signing or transaction submission during tests.

Deployment

Frontend-only release with retained rollback and public verification. Production activation remains gated on safe storage headroom and staged acceptance.