fix: use correct order for BTC network and fees cp-7.59.0

[SteP-n-s]

Description

Fix issue with incorrect network order & fees

Changelog

CHANGELOG entry: fix incorrect network order and fees

Related issues

Fixes: #22314

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Screen.Recording.2025-11-06.at.11.51.42.mov

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile 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

Sorts destination networks by popularity with BTC included and standardizes network fee display to fiat, with updated tests and e2e adjustments.

• Bridge UI
  • Network ordering: Export and use ChainPopularity to sort destination networks; add BTC (BtcScope.Mainnet) and adjust rankings; fallback to Infinity for unknown chains.
  • Dest selector: Apply popularity sort in BridgeDestNetworkSelector (excludes current chain unless Unified mode).
  • Snapshots/Tests: Update snapshots to reflect new order; add test for popularity fallback.
• Quote Data
  • Fees: Always format networkFee using fiat valueInCurrency (handles <$0.01, $0, and missing values as -); remove primary-currency/ticker-based formatting.
  • Unit Tests: Update and expand tests to cover new fee formatting cases and edge conditions.
• E2E
  • Adjust swipeNetwork to target updated ordering.

^{Written by Cursor Bugbot for commit fc761a6. 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.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[metamaskbot]

Missing release label release-7.59.0 on PR. Adding release label release-7.59.0 on PR and removing other release labels(release-7.60.0), as PR was cherry-picked in branch 7.59.0.