feat: bootstrap a reset notifications feat

[Jonathansoufer]

Description

This PR implements an ability of our users delete they NOTIFICATIONS' storage keys. This means they will delete all notifications history connected with that storage key. Users can enable Notifications again and so a new storage key will be created.

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

Screen.Recording.2024-09-27.at.14.30.30.mov

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]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/eth-hd-keyring@7.0.4	None	0	59.4 kB	metamaskbot
npm/@metamask/eth-simple-keyring@6.0.5	None	0	43.4 kB	metamaskbot
npm/@metamask/keyring-api@8.1.3	None	0	252 kB	metamaskbot
npm/@metamask/keyring-controller@17.2.2	None	0	538 kB	metamaskbot
npm/@metamask/notification-services-controller@0.8.2	network	0	1.22 MB	metamaskbot
npm/@metamask/profile-sync-controller@0.9.4	network	0	1.06 MB	metamaskbot

🚮 Removed packages: npm/@metamask/eth-hd-keyring@7.0.1, npm/@metamask/eth-simple-keyring@6.0.1, npm/@metamask/keyring-api@8.1.0, npm/@metamask/keyring-controller@17.2.1, npm/@metamask/notification-services-controller@0.8.0, npm/@metamask/profile-sync-controller@0.8.1

View full report↗︎

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: bfa1261
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8b9235a1-93fc-41a1-948b-7937697ff126

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: cf4a036
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1d9c32df-0c1c-44fa-981b-31ac89aeb6ad

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 335a00e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/583562d2-ee40-428c-99f2-69752afd1c44

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud