Use audit events for TIPS transaction views

[niran]

Summary

Replace the TIPS UI transaction data path with audit-archiver backed reads while preserving S3 fallback compatibility for deployments where audit-archiver has not been fully rolled out.

• Reads transaction, bundle, rejected transaction, and block event-history data from the audit JSON-RPC API via TIPS_UI_AUDIT_RPC_URL.
• Keeps S3-backed endpoints as fallbacks so existing functionality continues to work while audit-backed data becomes available.
• Keeps TIPS_UI_RPC_URL for canonical block and transaction details, including enriching bundle transactions from RPC instead of relying on synthetic audit payload fields.
• Joins bundle, transaction, payload, flashblock, and block-context audit events so bundle and block pages can show relevant event history.
• Displays event history on block pages and polishes block/bundle event rows with a compact timeline layout, consistent Block #N · FBM context, elapsed T + ... timing after the first event, source/target/reason chips, and a JSON expander button.
• Adapts current audit event payloads including SIMULATION_SUCCEEDED, SIMULATION_FAILED, BUILDER_REJECTED, metering responses, payload IDs, flashblock indices, and observability source metadata.

Verification

• bun test src/lib/audit-events.test.ts
• bun run build

Notes

• The audit API is preferred when available; S3 fallback remains intentionally present for compatibility during rollout.
• TIPS_UI_RPC_URL is still required for canonical transaction and block data enrichment.