refactor(bridge): use MMDS HeaderStandard

[brianacnguyen]

Description

Bridge Default and Custom slippage bottom sheets still used HeaderCompactStandard from component-library. This migrates both to HeaderStandard from @metamask/design-system-react-native so slippage UI follows the same header pattern as the rest of the app and reduces reliance on the temporary header component.

---

Changelog

CHANGELOG entry: null

---

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/DSYS-697

---

Manual testing steps

Feature: Bridge slippage modal header

  Scenario: Default slippage sheet shows expected header and closes
    Given the user is on the Bridge flow with slippage configurable

    When the user opens the default slippage modal
    Then the sheet title shows the slippage string (same as before)
    And the user can dismiss the sheet with the close control

  Scenario: Custom slippage sheet shows expected header and closes
    Given the user is on the Bridge flow with custom slippage available

    When the user opens the custom slippage modal
    Then the sheet title shows the slippage string (same as before)
    And the user can dismiss the sheet with the close control

---

Screenshots/Recordings

Before

After

---

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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

Low Risk
Low risk UI refactor limited to swapping header components and updating accessibility labels/translations; behavior changes should be confined to close button props and related tests.

Overview
Bridge slippage bottom sheets (default and custom) now use MMDS HeaderStandard instead of the temporary HeaderCompactStandard, wiring onClose through the new header API.

Adds a localized bridge.close string and updates modal tests to assert the header close button via accessibilityLabel from i18n rather than a hardcoded "Close" mock.

^{Reviewed by Cursor Bugbot for commit 566ed03. Bugbot is set up for automated code reviews on this repo. 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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeSwap, SmokeConfirmations
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 90%

click to see 🤖 AI reasoning details

E2E Test Selection:
The changes are narrowly scoped to the Bridge slippage modal UI components (CustomSlippageModal and DefaultSlippageModal). Both modals replace the temporary HeaderCompactStandard component with the stable HeaderStandard from @metamask/design-system-react-native, and add a closeButtonProps with an accessibility label using a new localization string bridge.close. The en.json change adds only this one new string under the bridge namespace. The test files are updated to remove the now-unnecessary mock for HeaderCompactStandard and use the new localization key for accessibility label lookups. These changes affect the Bridge/Swap slippage modal flow, which is part of the swap/bridge trading flows covered by SmokeSwap. Per the SmokeSwap tag description, SmokeConfirmations must also be selected since transaction confirmations are part of the swap flow. No other areas are impacted — no controller changes, no navigation changes, no shared component changes that would affect other flows.

Performance Test Selection:
The changes are purely UI component replacements in the slippage modal (HeaderCompactStandard → HeaderStandard). There are no changes to list rendering, data loading, state management, app initialization, or any other performance-sensitive areas. No performance tests are warranted.

View GitHub Actions results

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.86%. Comparing base (3751d9a) to head (566ed03).
⚠️ Report is 211 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #29700      +/-   ##
==========================================
+ Coverage   81.54%   81.86%   +0.32%     
==========================================
  Files        5343     5434      +91     
  Lines      142128   144898    +2770     
  Branches    32411    33093     +682     
==========================================
+ Hits       115899   118623    +2724     
+ Misses      18299    18166     -133     
- Partials     7930     8109     +179     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud