fix: enable earn button navigation on unsupported networks

[amitabh94]

Description

This PR fixes Earn CTA navigation behavior when clicked on unsupported networks. Previously, the button was unresponsive or navigated to Portfolio screen when clicked on networks that don't support staking. Now, it properly switches to mainnet and navigates to the staking UI.

Related issues

• Jira ticket: STAKE-916

Manual testing steps

1. Open the app and navigate to home page and select Portfolio View
2. Change the Network to Linea
3. Click on Earn button next to Ethereum in Portfolio View
4. It should change the network to mainnet and then navigate to staking UI

Screenshots/Recordings

Before

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-01-15.at.08.40.50.mp4

After

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-01-15.at.08.43.34.mp4

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.

[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]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: db2fb3c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/032c7873-e251-44ea-bb72-7931135119d6

Note

• This comment will auto-update when build completes
• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 1971ee3
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/82fe4be3-9d20-47f9-972e-0f0603b86be9

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 40.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 59.82%. Comparing base (faf5340) to head (1971ee3).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...mponents/UI/Stake/components/StakeButton/index.tsx	40.00%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12988      +/-   ##
==========================================
- Coverage   59.83%   59.82%   -0.02%     
==========================================
  Files        1873     1873              
  Lines       42121    42124       +3     
  Branches     5473     5474       +1     
==========================================
- Hits        25204    25201       -3     
- Misses      15235    15240       +5     
- Partials     1682     1683       +1     

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

[Matt561]

I've tested the fix successfully locally. LGTM!