fix: update inpage provider chainChanged, networkChanged, connect, and disconnect events

[jiexi]

Description

Previously the inpage provider would withhold events for chainChanged events (and property value updates, i.e. window.ethereum.chainId and .networkVersion) when the dapp's network was changed to an rpc endpoint that was unresponsive or did not support net_version. The dapp would instead receive a disconnect event.

Now the inpage provider always emits chainChanged and networkChanged events (and exposes the correct values on window.ethereum.chainId and .networkVersion) when the selected network for the dapp has changed regardless of if the network being changed to is responsive or if it supports net_version requests. It does this by having the wallet send a loading for networkVersion when it cannot be resolved (same behavior as before) AND a new isConnected property in the metamask_getProviderState request and metamask_chainChanged events (these are different from the events emittted by window.ethereum). isConnected is derived from whether the NetworkController.state.networkMetadata[].status value is the Available constant.

NOTE: this PR still needs the @metamask/providers changes linked below before it can be merged. To test manually you will need to manually build and copy the package dist into your local extension build node_modules

Related issues

Needs: MetaMask/providers#404
See: https://github.com/orgs/MetaMask/projects/146/views/1?filterQuery=label%3A%22team-wallet-api-platform%22+-status%3ABacklog&pane=issue&itemId=95374156&issue=MetaMask%7CMetaMask-planning%7C4039

Manual testing steps

window.ethereum.on('chainChanged', (data) => console.log('chainChanged', data))
window.ethereum.on('networkChanged', (data) => console.log('networkChanged', data))
window.ethereum.on('connect', (data) => console.log('connect', data))
window.ethereum.on('disconnect', (data) => console.log('disconnect', data))

1. Go to a dapp and enter the above in console
2. Using the wallet ui, switch the network for the dapp
3. When switching to a network without net_version support, networkChanged should be emitted by the inpage provider with null
4. When switching to a network that is not responsive, a disconnect event should be fired AND chainChanged and networkChanged should fire as well if those values have changed
5. When switching from an unresponsive network to a responsive network, a connect event should be fired AND chainChanged and networkChanged should fire as well if those values have changed
6. When switching to a network that was previously responsive that also supported net_version but is no longer responsive, a disconnect event should be fired and networkChanged should return the previously cached value

Screenshots/Recordings

Before

Screen.Recording.2025-01-27.at.4.13.46.PM.mov

After

Screen.Recording.2025-01-27.at.3.53.39.PM.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.

[metamaskbot]

Builds ready [5eea5ea]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

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

Page Load Metrics (1800 ± 92 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	398	2304	1719	356	171
		domContentLoaded	1457	2266	1767	188	90
		load	1495	2277	1800	192	92
		domInteractive	26	100	42	21	10
		backgroundConnect	10	133	34	29	14
		firstReactRender	15	101	45	29	14
		getState	4	92	21	24	12
		initialActions	0	0	0	0	0
		loadScripts	1033	1714	1292	165	79
		setupStore	8	64	20	19	9
		uiStartup	1718	2858	2091	303	146

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

• background: 139 Bytes (0.00%)
• ui: 0 Bytes (0.00%)
• common: 0 Bytes (0.00%)