refactor: centralize active kit filtering in KitManagerImpl

[denischilik]

Background

This refactor centralizes active-kit filtering in KitManagerImpl to reduce repeated listener checks and keep forwarding behavior consistent.

What Has Changed

• Replaced repeated providers.values() + disabled checks with activeKits() in push, lifecycle, identity, consent, and referrer callback paths.
• Standardized forwarding loops to remove duplicated listener filtering logic and repeated casts.
• Added a reusable typed helper (activeKitsOfType) and applied it to listener selection paths.

Screenshots/Video

N/A

Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have tested this locally.

[cursor]

PR Summary

Medium Risk
Refactors core kit-forwarding paths (push, commerce, lifecycle, identity/consent, referrer) to iterate only over active kits, which could subtly change which integrations receive callbacks if disabled-state handling differed previously.

Overview
Centralizes kit callback forwarding to only run against active (non-disabled) kits. Multiple forwarding loops in KitManagerImpl switch from iterating providers.values() with repeated isDisabled() checks to using activeKits().

This also standardizes listener casting using typed instanceof and introduces userAttributeListeners() to reuse active-kit + listener filtering, which is then used for consent/user-attribute related forwarding.

^{Reviewed by Cursor Bugbot for commit 99da62b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
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