feat(config-registry-controller)!: index configs by caip chain id

[mikesposito]

Explanation

The ConfigRegistryControllerState.configs.networks type is being narrowed down to Record<CaipChainId, RegistryNetworkConfig> instead of Record<string, RegistryNetworkConfig>

References

• Related to https://consensyssoftware.atlassian.net/browse/WPN-1562

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

---

Note

Medium Risk
Breaking TypeScript types for configs.networks and lookup parameters require consumer updates; runtime behavior is mostly unchanged aside from stricter chain ID validation on API responses.

Overview
BREAKING: Network configs in controller state are now keyed and typed as CaipChainId instead of arbitrary strings. ConfigRegistryControllerState.configs.networks becomes Record<CaipChainId, RegistryNetworkConfig>, and getNetworkConfigByCaip2ChainId takes a CaipChainId argument.

Registry API parsing now validates each chain’s chainId with CaipChainIdStruct from @metamask/utils, so only CAIP-2-shaped IDs (e.g. eip155:1) are accepted at the type/schema layer. The changelog documents the breaking state shape change and ties it to the existing lookup API.

^{Reviewed by Cursor Bugbot for commit 8c8a1f8. Bugbot is set up for automated code reviews on this repo. Configure here.}