Description

This PR updates the headers in the receive flow to use the newer HeaderCenter component from component-library/components-temp.

What is the reason for the change?
The getAddressListNavbarOptions function in Navbar/index.js was a one-off navbar utility that duplicated functionality already available in the HeaderCenter component.

What is the improvement/solution?

• Replaced getAddressListNavbarOptions with getHeaderCenterNavbarOptions in AddressList.tsx
• Replaced BottomSheetHeader with HeaderCenter in ShareAddressQR.tsx
• Removed the now-unused getAddressListNavbarOptions function and its tests from Navbar/index.js

This consolidates header patterns and reduces code duplication by leveraging the reusable HeaderCenter component.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MDP-655?atlOrigin=eyJpIjoiNzhiOTE5OWVlN2NkNDIxZDhjMzI3MGJlYTQ4OTU2NDkiLCJwIjoiaiJ9

Manual testing steps

Feature: Receive Flow Headers

  Scenario: user views the address list screen
    Given user is logged in and on the wallet home screen
    When user navigates to the receive flow and opens the address list
    Then the header should display with a back button and centered title
    And tapping the back button should navigate back

  Scenario: user views the share address QR sheet
    Given user is logged in and on the wallet home screen
    When user opens the share address QR bottom sheet
    Then the header should display with the account group and network name
    And tapping the back button should close the sheet

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.

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.