chore: add eventListenerService [WPB-23186]

[e-maad]

WPB-23186 [Web] Applock forgot password - Users prompted to log out, log in, set new applock password

Summary

Add eventListenerService for purify functions and pass window.eventListener as a dependency.

Security Checklist (required)

• External inputs are validated & sanitized on client and/or server where applicable.
• API responses are validated; unexpected shapes are handled safely (fallbacks or errors).
• No unsafe HTML is rendered; if unavoidable, sanitization is applied and documented where it happens.
• Injection risks (XSS/SQL/command) are prevented via safe APIs and/or escaping.

Accessibility (required)

• I have read and this PR upholds our Accessibility Best Practices.

Standards Acknowledgement (required)

• I have read and this PR upholds our Coding Standards and Tech Radar Choices.

---

Screenshots or demo (if the user interface changed)

Notes for reviewers

• Trade-offs:
• Follow-ups (linked issues):
• Linked PRs (e.g. web-packages):

[github-actions]

🔗 Download Full Report Artifact

🧪 Playwright Test Summary

• ✅ Passed: 14
• ❌ Failed: 0
• ⏭ Skipped: 0
• 🔁 Flaky: 0
• 📊 Total: 14
• ⏱ Total Runtime: 754.6s (~ 12 min 35 sec)

[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

[zskhan]

Mutating the same array inside a loop will skip the some array elements.
[eventOnce, event1, event2]
if you remove eventOnce after the first iteration then event1 will be skipped in the second iteration as it will be on index 0 and on index 1 it will be event2.
So we can store the events to be removed on another array and delete it after the loop.

[screendriver]

I'm not convinced this module is a useful abstraction in its current form. To me this reads more like a generic event-emitter-style wrapper than a clean architecture boundary. eventListenerService is essentially a thin wrapper around global event APIs and deterministicEventListenerService adds another generic listener layer on top, but without making the domain model clearer.

I also find the name deterministic misleading here. In this context, determinism usually refers to controlling sources of runtime variability such as time, network responses, randomness, retries, or scheduling. This implementation does not seem to address that kind of nondeterminism; it mainly provides synchronous in-memory listener dispatch.

I'm also concerned about the typing. Accepting arbitrary string event names and generic Event values means the compiler cannot help us validate that subscriptions and dispatched payloads actually match.

My preference would be to keep global/browser event registration at the application entry point and pass concrete function callbacks inward into the application layer. That keeps the browser-specific wiring at the edge, makes dependencies explicit and gives us better type safety than introducing a generic event-listener abstraction.