feat: rFOX arbitrum Txs parser

[gomesalexandre]

Description

Adds unchained-client parsing for rFOX Txs on Arbitrum.

Pull Request Type

• 🐛 Bug fix (Non-breaking Change: Fixes an issue)
• 🛠️ Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
• 💅 New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #7120

Risk

High Risk PRs Require 2 approvals

Low - ensure the right guards are in place in unchained-client parsing so this early bails on Txs other than rFOX ones.

What protocols, transaction types or contract interactions might be affected by this PR?

Testing

• rFOX Txs are parsed (see screenshot)

Engineering

• ☝🏽

Operations

• ☝🏽

Screenshots (if applicable)

[kaladinlight]

I added a couple of updates:

• Test mocks use exact return data from unchained api
• Update tests to use the from address to show correct fees and transfers
• Add extra metadata for runeAddress and claimIndex (claimIndex unused currently)
• Add rune address to transaction row
• Add unstake amount to transaction row
• Update unstake to unstakeRequest so it doesn't show as a receive transaction
• Extend TransactionDetails/Amount.tsx to support assetId (let me know if you know a better component for crypto amount with assetId to control symbol and precision)

[gomesalexandre]

I added a couple of updates:

@kaladinlight can't stamp my own PR but looks perf, get in!