feat: upgrade assets controllers to version 44

[bergeron]

Description

Upgrades the assets controllers to version 44. And starts replacing some instances of https://github.com/MetaMask/eth-token-tracker with reading state from the TokenBalancesController

Related issues

Manual testing steps

No visual changes. Token balances should render correctly like before on the tokens page, and when switching accounts and chains.

Screenshots/Recordings

Before

After

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.

[bergeron]

This looks like the values are changing, but it actually keeps them (mostly) the same. The old behavior of mocking ./useTokenTracker was modifying this array during the test, so this just updates to the same final result.

[bergeron]

We don't have an easy way to replicate the loading flag. Both because the token balances controller doesn't currently set any state indicating an update is in progress. And because in the multichain world, it may not be a single request we're waiting on. Each network will update and return separately. We don't have UI to indicate that specific balances are loading.

[bergeron]

Reading balances from state will have some UI benefits though. Since we don't have to wait for requests to return, we can always immediately show what we have in state, without an initial 'loading' flash. The values may be stale though, so in the future we may want to indicate which balances are very stale. Perhaps the controller could timestamp in state the time of the last update for each balance.

[metamaskbot]

Builds ready [613a07a]

• 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, 7
  • 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, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (2019 ± 57 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1859	2323	2026	121	58
		domContentLoaded	1829	2243	1981	111	53
		load	1850	2327	2019	119	57
		domInteractive	32	173	52	32	15
		backgroundConnect	9	95	36	26	13
		firstReactRender	52	287	137	73	35
		getState	43	255	128	63	30
		initialActions	0	1	0	0	0
		loadScripts	1342	1745	1510	102	49
		setupStore	6	82	17	21	10
		uiStartup	2092	2999	2506	266	128

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 919 Bytes (0.01%)
• ui: 2.2 KiB (0.03%)
• common: 18.7 KiB (0.23%)