feat: bump @metamask/notification-services-controller to 2.0.0

[Prithpal-Sooriya]

Description

Bumps @metamask/notification-services-controller@2.0.0.

Related issues

Fixes: #13838

Manual testing steps

This is a build release, no changes are introduces to the notification flow.

Test Notifications Feature:

1. Enable/Disable Notifications
   1. Onboard Wallet
   2. Click Bell Icon and enable notifications
   3. Visit Notification Settings and disable notifications
2. Enable/Disable Account Notification Settings
   1. Visit Notification Settings and enable/disable notifications for an account

Screenshots/Recordings

Before

After

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]

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]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/notification-services-controller@1.0.0 ➜ 2.0.0	None	0	1.37 MB	metamaskbot

View full report↗︎

[sonarqubecloud]

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 SonarQube Cloud

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 0dddb04
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/98cad572-96a9-4dcc-99b1-ab95a302eb98

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise