Fix signTypedData_v4 chainId validation

[rekmarks]

We were checking the chainId passed with signTypedData_v4 requests against NetworkController.network, which is wrong. This PR ensures that we check it against the stored chainId.

Fixes #8385

[metamaskbot]

Builds ready [876ce04]

• builds: chrome, firefox, opera
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• dep viz: background
• all artifacts

Page Load Metrics (433 ± 52 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	32	93	52	22	11
		domContentLoaded	322	691	431	109	52
		load	323	693	433	109	52
		domInteractive	322	690	431	109	52

[metamaskbot]

Builds ready [876ce04]

• builds: chrome, firefox, opera
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• dep viz: background
• all artifacts

Page Load Metrics (377 ± 38 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	29	104	39	16	7
		domContentLoaded	294	594	376	80	38
		load	296	595	377	80	38
		domInteractive	294	592	375	80	38

[danfinlay]

This looks good to me, glad we're finally using the semantic meaning of chainId instead of networkId's "usually the same" behavior.

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

The base branch was changed.

[metamaskbot]

Builds ready [06c0da6]

• builds: chrome, firefox, opera
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• dep viz: background
• all artifacts

Page Load Metrics (443 ± 49 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	30	49	38	4	2
		domContentLoaded	309	697	441	101	49
		load	310	699	443	101	49
		domInteractive	309	697	441	101	49

[Gudahtt]

LGTM!