chore: add whitelist to utils to ignore warnings for specific networks

[Julink-eth]

Explanation

Add a list of networks that will be treated as whitelisted not to display the warning messages in the clients (Extension/Mobile) when adding them as custom networks.
This list is starting with HyperEVM network.

References

Related to MetaMask/metamask-mobile#19167
Related to MetaMask/metamask-extension#35609

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[mcmire]

I have made some suggestions as it relates directly to these changes. However, have we considered porting over the chain collision check from the clients itself rather than just the mapping? If the goal is to consolidate the behavior around network validation then it seems like that would satisfy the goal in a more maintainable way. As it is, if we just bring over the mapping, we are allowing the behavior to deviate (because developers could use this constant in a way that wasn't intended, or worse, not use it at all).

[mcmire]

LGTM!