fix: don't show banner if preferences exist

[iamacook]

What it solves

Resolves #2592 (comment)

How this PR fixes it

The notification registration banner now takes into account whether the current Safe is registered before being displayed.

How to test it

1. Ensure a Safe is added and not registered for notifications.
2. Open the Safe in question but don't dismiss the notification registration banner.
3. Open the notification settings for that Safe.
4. Register for notifications.
5. Observe the banner close.
6. Reopening that Safe should not show the banner until it is "unregistered" for notifications.

Screenshots

Checklist

• I've tested the branch on mobile 📱
• I've documented how it affects the analytics (if at all) 📊
• I've written a unit/e2e test for it (if applicable) 🧑‍💻

[github-actions]

Branch preview

✅ Deploy successful!

https://notification_banner_preferences--walletweb.review-wallet-web.5afe.dev

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[katspaugh]

Could you rename isNotificationsEnabled to something like isFeatureEnabled? It's confusing wrt user enabling notifications/allowing push notifications.

[schmanu]

Looks good to me. We could consider writing a test for the Banner component as it's complexity grew a bit.

[francovenica]

Looks good.

The pop up dissapears if you enable notifications in the safe settings
The pop up doesn't show if you enable the notifications from the global settings and then visit the safe.