fix: use chainId-based native currency in transaction display hooks

[fly-1-1]

Description

This PR fixes currency display issues in transaction display hooks by ensuring the use of chainId-based native currency instead of relying solely on account-based currency.

Problem:
In multi-chain scenarios, the current transaction display logic only relies on account information to determine native currency, which can lead to incorrect currency symbols and conversion rates being displayed on different chains.

Solution:

• Introduce effectiveNativeCurrency logic in the useCurrencyDisplay hook to prioritize chainId-based native currency
• Properly pass chainId parameters to related currency display hooks in useTransactionDisplayData
• Ensure conversion rate calculations are also based on the correct chainId

Changelog

CHANGELOG entry: Fixed transaction display to use correct chain-specific native currency symbols and conversion rates

Related issues

Fixes:

Manual testing steps

1. Switch to different blockchain networks (e.g., Ethereum Mainnet, Polygon, etc.)
2. Initiate a transaction or view transaction history
3. Verify that the currency symbols displayed in transaction details correspond to the current chain's native currency
4. Check that conversion rates use the correct chain's rates
5. Verify currency display consistency in transaction lists and transaction detail pages

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Ensure currency symbols and conversion rates are resolved by transaction chainId across currency/token display hooks.

• Hooks: chain-aware currency resolution
  • ui/hooks/useCurrencyDisplay.js:
    • Add effectiveNativeCurrency using chainId (fallback to account native currency).
    • Determine isNativeCurrency with chainId-aware checks.
    • Use chainId-scoped currencyRates to derive effectiveConversionRate.
    • Apply effectiveNativeCurrency/effectiveConversionRate in conversions and ETH display; update memo deps.
  • ui/hooks/useTokenFiatAmount.js:
    • Use chainId-specific market data and tokenConversionRate from currencyRates + networkConfigurationsByChainId.
    • Include formatted in memo deps.
  • ui/hooks/useTransactionDisplayData.js:
    • Derive txChainId and pass to useTokenFiatAmount, useUserPreferencedCurrency (PRIMARY/SECONDARY), and useCurrencyDisplay.
• Result: Transaction and token displays use correct chain-native symbols and fiat rates.

^{Written by Cursor Bugbot for commit c7f9ce4. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[fly-1-1]

I have read the CLA Document and I hereby sign the CLA