Release 1313.0.0

[gauthierpetetin]

Release of (after this PR got merged):

• @metamask/analytics-controller (major): 3.2.0 → 4.0.0
• @metamask/config-registry-controller (major): 4.0.0 → 5.0.0
• @metamask/wallet (patch): 16.0.0 → 16.0.1

And release of their dependents:

• @metamask/assets-controller (patch): 18.0.0 → 18.0.1
• @metamask/network-controller (patch): 37.0.0 → 37.0.1
• @metamask/network-enablement-controller (patch): 7.0.1 → 7.0.2

---

Note

Medium Risk
The release propagates major analytics and config-registry changes with breaking messenger wiring across network-controller and wallet; integrators must update delegations even though this PR only changes versions and changelogs.

Overview
This is a monorepo release (1312.0.0 → 1313.0.0) that cuts new package versions and threads updated dependency ranges through the workspace and yarn.lock—no application source changes in this diff.

Headline releases: @metamask/analytics-controller 4.0.0 and @metamask/config-registry-controller 5.0.0 (majors whose changelogs carry breaking messenger requirements: analytics must allow ConfigRegistryController:getState / stateChanged; config registry must allow ConfigRegistryApiService:fetchEventsConfig and caches /v1/config/events-config in state). @metamask/network-controller 37.0.1 depends on those majors, so upgrading network ripples the same constraints to most controllers.

Patch releases: @metamask/wallet 16.0.1, @metamask/assets-controller 18.0.1, and @metamask/network-enablement-controller 7.0.2 mainly record dependency alignment on network-controller 37.0.1 and/or config-registry-controller 5.0.0. Dozens of packages bump @metamask/network-controller to ^37.0.1; consumers of @metamask/wallet-cli also pick up @metamask/wallet 16.0.1 and analytics/config-registry majors.

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