feat: migrate to native primary currency

[salimtb]

Description

The primary currency toggle provides unnecessary overhead for every asset feature we build. The Extension team is removing it for Extension and we will do so as well for Mobile.
the default one on mobile will be Native.

Related issues

Fixes: #1846

Manual testing steps

1. Go the setting page
2. Go to general
3. Primary currency toggle is removed, the default one is Native

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• 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.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0602c987-5a60-45c1-ac43-73c4a8d1b53a
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 43.77%. Comparing base (4de7cef) to head (1f8f04f).
Report is 10 commits behind head on main.

❗ Current head 1f8f04f differs from pull request most recent head 4835a60. Consider uploading reports for the commit 4835a60 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8720      +/-   ##
==========================================
+ Coverage   43.74%   43.77%   +0.02%     
==========================================
  Files        1273     1274       +1     
  Lines       31103    31124      +21     
  Branches     3161     3168       +7     
==========================================
+ Hits        13606    13623      +17     
- Misses      16684    16688       +4     
  Partials      813      813              

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

[github-actions]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/17d52963-c977-454a-9269-849bbfdbb795
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[github-actions]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/6bdf4db5-c5c2-469d-8f74-4bad5666bc11
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[cortisiko]

Hey @salimtb a few more test scenarios come to mind:

• Changing your currency conversion from USD to CAD and submit a txn
• Change your currency conversion from USD to DAI, ETC and submit a txn

Does this PR require migrations? If so here is another scenario to test:

• Test with a version of the app where you select Fiat as your primary currency
• Upgrade to the app with this version. Does the app break? try visiting the general view does the app break? Try to submit another txn.

[salimtb]

hey @cortisiko ,
you can find here the list of requested test

[cortisiko]

@salimtb, I have reviewed your testing.

The idea of removing the fiat toggle makes sense to me. I'm concerned that omitting the fiat conversion of the total transaction amount on the confirmation screen could cause user confusion.

see this video at the 17-19 second mark

[cortisiko]

Thanks for providing testing artifacts @salimtb. Everything looks ✅ from a quality perspective.

changes was addressed

[Cal-L]

Left some comments

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[Cal-L]

LGTM!