fix: migration 43 stringify to type of

[tommasini]

Description

typeof rather than stringily here because this would result in a great deal of data in our error message. This is problematic for two reasons: it means that each unique network configuration gets interpreted as a unique error by Sentry, no grouping. And it potentially exposes private information.

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

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

[Gudahtt]

LGTM!

[sethkfman]

LGTM

[metamaskbot]

No release label on PR. Adding release label release-7.24.3 on PR, as PR was added to branch 7.24.3 when release was cut.