Jl/version v12 10.4/hotfix network version inpage provider

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

Related issues

See: #29936
Providers patch from commit (d919ab6b): MetaMask/providers#404

Manual testing steps

window.ethereum.on('accountsChanged', (data) => console.log('accountsChanged', data))
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 webpage. Enter the following in console
2. Change to Linea, see that the correct values are emitted for the chainChanged and networkChanged events
3. Change to Sepolia, see that the correct values are emitted for the chainChanged and networkChanged events
4. Change to a network that is non-responsive, see that chainChanged emits with the correct chainId, but networkChanged emits with a null value, AND there is a disconnect event emitted
5. Change back to a working network, see that the correct values are emitted for the chainChanged and networkChanged events, AND there is a connect event emitted with the new chainId
6. Do the same above with a responsive network that does not have net_version implemented. Se that the correct values are emitted for the chainChanged, that networkChanged emits null, and that there is no disconnect event emitted

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.

[jiexi]

closed in favor of #30111

[metamaskbot]

Builds ready [ef7c966]

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

Page Load Metrics (1824 ± 56 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	313	2032	1681	435	209
		domContentLoaded	1585	1995	1792	122	59
		load	1628	2017	1824	117	56
		domInteractive	28	117	48	23	11
		backgroundConnect	9	79	28	22	10
		firstReactRender	16	106	36	25	12
		getState	5	55	14	14	7
		initialActions	0	1	0	0	0
		loadScripts	1159	1495	1327	107	52
		setupStore	6	73	22	22	11
		uiStartup	1824	2576	2107	176	84