chore: Add primary currency to user object in MetaMetrics

[gambinish]

Description

Attaches the primary currency selection from Settings to the user object and emits a new event. Will also need to be tracked in the extensions repo (PR coming soon)

Related issues

Fixes: MMASSETS-283

Github Issue: #10573

Manual testing steps

1. Go to settings page
2. Toggle Fiat and Native currency toggles
3. Validate that events are being emitted as expected

Screenshots/Recordings

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 failed on Bitrise! ❌❌❌

Commit hash: e981b5a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/94252a46-618b-45f0-9a8e-fed18246f865

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: b988945
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/6a9c2bf8-a840-4bf2-b073-fcbcd8fd355a

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: f7b857d
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5312b7a0-59d5-4e40-9934-0fd037265e44

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: e52cf4d
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f0f9b8c6-4c19-4c95-b665-daf95739ff9d

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

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

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 50.59%. Comparing base (4b9f31c) to head (bd40405).
Report is 70 commits behind head on main.

Files	Patch %	Lines
...components/Views/Settings/GeneralSettings/index.js	0.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10490      +/-   ##
==========================================
+ Coverage   49.78%   50.59%   +0.80%     
==========================================
  Files        1437     1506      +69     
  Lines       34762    35914    +1152     
  Branches     3921     4121     +200     
==========================================
+ Hits        17307    18171     +864     
- Misses      16354    16585     +231     
- Partials     1101     1158      +57     

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: bd40405
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f7380af9-6f1b-41d1-8c8f-83e5c5d4deea

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

[salimtb]

hey @gambinish , can you pls create a github issue ( with the same description than the Jira ) and attach it on this PR.
for mobile this is the standard we follow

[gambinish]

hey @gambinish , can you pls create a github issue ( with the same description than the Jira ) and attach it on this PR. for mobile this is the standard we follow

Added. Is this needed for every mobile PR?