feat: add references and utils for delete storage key

[Jonathansoufer]

Description

This PR implements a feature for our users get access to delete their Notification's storage keys if need.

Related issues

Fixes:

Manual testing steps

1. Go to Settings
2. Choose Notifications
3. Make sure its enabled
4. Click on Reset Notifications
5. Proceed
6. Check if Notifications remain enabled and a toast is shown.

Screenshots/Recordings

Before

After

Screen.Recording.2024-10-10.at.13.59.18.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/profile-sync-controller@0.9.7	network	0	1.11 MB	metamaskbot

🚮 Removed packages: npm/@metamask/profile-sync-controller@0.9.5

View full report↗︎

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 9f36768
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c9fb085f-6a0d-4d44-9f9b-5613d0c6e36a

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

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarCloud

[tommasini]

Can you add manual steps to the PR description please? It will be easier to test on release that way!