feat: add preference for user to enable smart account opt-in

[jpuri]

Description

Adding preference for user to opt in for smart account upgrade. It will be enabled by default for new users.

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/5235

Manual testing steps

1. Go to advance settings and opt in for smart account upgrade
2. Splash pages should no longer be visible for the user when submitting batch request

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​metamask/​preferences-controller@​18.2.0 ⏵ 18.4.0	+2		+1	+4

View full report

[Cal-L]

left comments

[codecov-commenter]

Codecov Report

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

Project coverage is 72.36%. Comparing base (d838bb0) to head (4a3193e).
Report is 48 commits behind head on main.

Files with missing lines	Patch %	Lines
app/store/migrations/088.ts	82.35%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16745      +/-   ##
==========================================
+ Coverage   72.19%   72.36%   +0.17%     
==========================================
  Files        2686     2703      +17     
  Lines       58160    58665     +505     
  Branches     9129     9221      +92     
==========================================
+ Hits        41989    42455     +466     
- Misses      13498    13528      +30     
- Partials     2673     2682       +9     

☔ 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.

[Cal-L]

LGTM

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b14cdcc
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b114db75-ac5c-40b0-98fc-aa25cac7e28d

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
86.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud