chore(deps): Bump `@metamask/controller-utils` from `^10.0.0` to `^11.3.0`

[MajorLift]

Description

• No changes to lockfile.
• 11.3.0 is already in use by dependencies.

Remaining Outdated Usage

All of the following will be updated shortly. Progress on this is being tracked here: https://github.com/MetaMask/MetaMask-planning/issues/3234

• swaps-controller is on the latest version. Requires new upstream release with updated deps.

v10

   ├─ @metamask/signature-controller@npm:17.0.0 [abc9d] (via npm:^17.0.0 [abc9d])
   │  ├─ @metamask/controller-utils@npm:10.0.0 (via npm:^10.0.0)
   │  └─ @metamask/message-manager@npm:9.0.0 (via npm:^9.0.0)
   │     └─ @metamask/controller-utils@npm:10.0.0 (via npm:^10.0.0)

v9

   ├─ @metamask/logging-controller@npm:3.0.1 (via npm:^3.0.0)
   │  └─ @metamask/controller-utils@npm:9.1.0 (via npm:^9.0.1)

   ├─ @metamask/phishing-controller@npm:9.0.2 (via npm:^9.0.0)
   │  └─ @metamask/controller-utils@npm:9.1.0 (via npm:^9.1.0)

   ├─ @metamask/assets-controllers@npm:30.0.0 [abc9d] (via npm:^30.0.0 [abc9d])
   │  ├─ @metamask/controller-utils@npm:10.0.0 (via npm:^10.0.0)
   │  └─ @metamask/polling-controller@npm:6.0.2 [32524] (via npm:^6.0.2 [32524])
   │     └─ @metamask/controller-utils@npm:9.1.0 (via npm:^9.1.0)

   ├─ @metamask/preferences-controller@npm:11.0.0 [abc9d] (via npm:^11.0.0 [abc9d])
   │  └─ @metamask/controller-utils@npm:9.1.0 (via npm:^9.1.0)

v8

   ├─ @metamask/ppom-validator@npm:0.32.0 (via npm:0.32.0)
   │  ├─ @metamask/controller-utils@npm:8.0.4 (via npm:^8.0.1)
   │  └─ @metamask/network-controller@npm:17.2.1 (via npm:^17.0.0)
   │     └─ @metamask/controller-utils@npm:8.0.4 (via npm:^8.0.4)

   ├─ @metamask/swaps-controller@npm:9.0.12 [abc9d] (via npm:^9.0.12 [abc9d])
   │  ├─ @metamask/controller-utils@npm:8.0.4 (via npm:^8.0.2)
   │  └─ @metamask/gas-fee-controller@npm:12.0.0 [4fe0f] (via npm:^12.0.0 [4fe0f])
   │     ├─ @metamask/controller-utils@npm:8.0.4 (via npm:^8.0.1)
   │     └─ @metamask/polling-controller@npm:4.0.0 [b6d7f] (via npm:^4.0.0 [b6d7f])
   │        └─ @metamask/controller-utils@npm:8.0.4 (via npm:^8.0.1)

Related issues

• Closes: https://github.com/MetaMask/metamask-mobile/issues/11048

Manual testing steps

Screenshots/Recordings

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[bot]]

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.

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/controller-utils@11.3.0	network	0	259 kB	danfinlay, gudahtt, kumavis, ...8 more

🚮 Removed packages: npm/@metamask/controller-utils@10.0.0

View full report↗︎

[github-actions[bot]]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 79494ab02a05f6d8ed1088937a907569f91b702e Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a362534e-f9f0-4f2a-b8b6-83e6d4ef396f

[!NOTE]

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud