feat!: allow dynamic infura networks

[mikesposito]

Explanation

Currently, NetworkController manages two types of network config: Infura and Custom. The Infura type is dedicated to configurations with RPC endpoints with an Infura URL that uses a template string for the project ID, while Custom configurations are generic network configurations that can be also added by users.

In order to add a network configuration of Infura type to NetworkController, the network must first be added to @metamask/controller-utils to satisfy NetworkController validations, or else it won’t be recognized as a known network, and the operation will fail with an error. This currently blocks us from leveraging mm-config-registry (Dynamic registry) from being used to add Infura network configurations remotely.

This PR relaxes NetworkController validations to accept Infura configurations that are not included in @metamask/controller-utils, nor in any other bundled known list.

References

• Fixes https://consensyssoftware.atlassian.net/browse/WPN-1554

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
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

[mikesposito]

@metamaskbot publish-preview