fix: refactor and fix notify bell hover logic

[fadi-george]

Description

1 Line Summary

Address: https://app.asana.com/1/780103692902078/project/1208777190614537/task/1213013500097033
Refactor and fix the notify bell component, resolving a tooltip race condition and simplifying CSS/JS.

Details

This overhauls the bell (notify button) prompt. Major areas of change:

• Replaced SCSS stylesheets with plain CSS, using CSS Anchor Positioning and the Popover API for layout and dialog behavior
• Removed AnimatedElement base class and simplified all bell sub-components (Launcher, Button, Badge, Message, Dialog)
• Replaced the internal event system with direct method calls between components
• Fixed a race condition where the tooltip/message would stay visible indefinitely. The old code had async _Hovering/_Hovered event handlers sharing a _hovering flag. If _show() resolved before the _Hovered (mouse-leave) handler ran, _hovering was already false, so the hide was never scheduled. This refactor removes that pattern entirely in favor of a simple mouseleave listener that blurs the button.
• Fixed several other UI bugs: dialog image sizing, hover state persistence when button focused, transform origin centering, message display timing, and prenotify on blocked permissions
• Added test coverage for Bell, Dialog, Launcher, Badge, Button, Message, and Slidedown with minimum coverage thresholds

Screenshots/Videos

Hover / Click

Screen.Recording.2026-03-04.at.12.43.05.AM.mov

With tooltip hover

Regular

Positioned Right

Custom Colors

---

---

---

Systems Affected

• WebSDK
• Backend
• Dashboard

Validation

Tests

Info

Added and expanded unit tests across all bell sub-components. Coverage thresholds configured in vitest.config.ts.

Checklist

• All the automated tests pass or I explained why that is not possible
• I have personally tested this on my machine or explained why that is not possible
• I have included test coverage for these changes or explained why they are not needed

Programming Checklist
Interfaces:

• Don't use default export
• New interfaces are in model files

Functions:

• Don't use default export
• All function signatures have return types
• Helpers should not access any data but rather be given the data to operate on.

Typescript:

• No Typescript warnings
• Avoid silencing null/undefined warnings with the exclamation point

Other:

• Iteration: refrain from using elem of array syntax. Prefer forEach or use map
• Avoid using global OneSignal accessor for context if possible. Instead, we can pass it to function/constructor so that we don't call OneSignal.context

Screenshots

Info

N/A - visual behavior validated manually via playground.

Checklist

• I have included screenshots/recordings of the intended results or explained why they are not needed

---

Related Tickets

https://app.asana.com/1/780103692902078/project/1208777190614537/task/1213013500097033

---

---

This change is 

[abdulraqeeb33]

Its a lot of changes @fadi-george . can we do a small bug bash around this?