refactor: migrate {NotificationServices,NotificationServicesPush}Controller to @metamask/messenger

[cryptodev-2s]

Explanation

This PR migrates NotificationServicesController and NotificationServicesPushController to the new @metamask/messenger message bus, as opposed to the one exported from @metamask/base-controller.

References

• Related to Implement messenger delegation #5626

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

---

Note

Migrates Notification Services controllers to the new @metamask/messenger, updates metadata flag, and adjusts tests/configs accordingly.

• Notification Services:
  • Migrate NotificationServicesController and NotificationServicesPushController from RestrictedMessenger (@metamask/base-controller) to Messenger (@metamask/messenger), updating all call/subscribe/publish/registerActionHandler usages.
  • Switch imports to @metamask/base-controller/next for BaseController and deriveStateFromMetadata.
  • Rename state metadata flag from anonymous to includeInDebugSnapshot in code and tests.
  • Remove package-level exports of AllowedActions/AllowedEvents; keep as internal types.
  • Update tests and mock messengers to use namespaced root messenger and delegation.
• Dependencies/Config/Docs:
  • Add dependency on @metamask/messenger@^0.3.0; add TS project references to packages/messenger.
  • Update README dependency graph to show notification_services_controller --> messenger and add eip_7702_internal_rpc_middleware --> controller_utils.
  • Update CHANGELOG with breaking changes.

^{Written by Cursor Bugbot for commit 6b8f905. This will update automatically on new commits. Configure here.}

[mcmire]

LGTM!