feat(frontend): use historical contract input decoding

[alez04]

Summary

This updates the explorer transaction details flow to use epoch-aware historical contract input decoding.

What changed

• switched contract input decoding from the current-only contracts registry to the versioned historical registry
• wired tickNumber -> epoch resolution into useDecodedContractInput
• passed tickNumber from TransactionDetails into the decode hook
• updated the frontend dependency to @qubic.ts/contracts@^1.3.0
• included the corresponding pnpm-lock.yaml refresh

Why

The previous frontend integration decoded smart-contract inputs against the current registry only.
That can misdecode or fail for transactions from older epochs when contract layouts changed.

With this change, the explorer resolves the transaction epoch first and then decodes against the contract version active for that epoch.

Validation

Code changes are scoped to the contract input decoding path and transaction details wiring.