Update NotificationServicesController to accommodate for Snaps Notifications

[hmalik88]

Explanation

• What is the current state of things and why does it need to change? We currently have snap types living in the extension, which should exist in this repo instead. Also, the extension is using two controllers to handle notifications, the NotificationController solely exists for the purpose of snap notifications. With the revamping of the notifications system, it is best to house all notifications in one place.
• What is the solution your changes offer and how does it work? Add snap logic to the NotificationServicesController
• Are there any changes whose purpose might not obvious to those unfamiliar with the domain? The updateMetamaskNotificationsList function will be the gateway for snaps to add notifications to the controller.

Changelog

@metamask/notification-services-controller

• ADDED: getNotificationsByType to grab a list of notifications by type.
• ADDED: deleteNotificationById to delete a notification in the controller's state (to be only used by notifications that live in this controller which currently is just snaps).
• CHANGED: fetchAndUpdateMetamaskNotifications to grab snaps from state before repopulating with a new list of other notifications.
• CHANGED: markNotificaftionsAsRead to account for snaps notifications.
• CHANGED: updateMetamaskNotificationsList to assign a processed notification to state instead of the originally passed in notification as the processSnapNotification function adds on extra properties to the raw notification.

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 highlighted breaking changes using the "BREAKING" category above as appropriate
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[socket-security]

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: npm/@metamask/[email protected]

View full report↗︎

[hmalik88]

CODEOWNER reviews are being triggered because I used the latest version of @metamask/utils in the NotificationServicesController and was required to update the rest of the packages as well to be in parity. There are no breaking changes from 9.1.0 -> 9.3.0

EDIT: Split the bumps into a different PR

[Prithpal-Sooriya]

Looks good, some initial comments.

I think we can move forward with this after our sync session.