fix: import all detected tokens automatically

[sahar-fehri]

Description

Now that we have most users autodetect tokens, we can make the UX even more streamlined. This PR automatically add in tokens we detect on behalf of users.

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MMASSETS-439

Manual testing steps

1. import an account that have tokens
2. Notice that tokens are imported automatically

Make sure the token detection is working properly:

1. Go to settings and turn off "autodetect tokens" setting
2. Add a new account that have tokens
3. Notice tokens are not added unless you turn the setting back ON

Screenshots/Recordings

Before

Screen.Recording.2024-12-20.at.11.28.14.mov

After

Screen.Recording.2024-12-20.at.11.25.27.mov

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension 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.

[salimtb]

tested with and without the feature flag on , works as expected , PR approved but you need to check the failing e2e test

[metamaskbot]

Builds ready [eae8fbb]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 12, 13, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1686 ± 95 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	273	2040	1606	354	170
		domContentLoaded	1433	2047	1666	200	96
		load	1441	2053	1686	198	95
		domInteractive	27	84	41	14	7
		backgroundConnect	8	52	17	12	6
		firstReactRender	16	74	31	22	11
		getState	4	73	29	23	11
		initialActions	0	0	0	0	0
		loadScripts	1029	1543	1245	163	78
		setupStore	6	55	13	12	6
		uiStartup	1592	2337	1923	211	101

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 1.48 KiB (0.02%)
• common: 0 Bytes (0.00%)

[bergeron]

I think this should have a check for whether there are any detected tokens. Otherwise it's doing an unnecessary call to the controller + state update on each load.

[bergeron]

maybe just changing the else to else if (detectedTokens?.length > 0) {