[QA] SDK | triggerAreas onExit not triggering when user leaves scene

### Build version
Not specified

### Issue Description
`triggerAreas` natively sense local user and also other users connected to the scene. When another user enters the area, `onTriggerEnter` fires correctly on the local scene. However, if that user disconnects or teleports to another scene while inside the area, `onTriggerExit` is never fired, leaving the trigger in a permanently entered state.

### STR (Steps to Reproduce)
1. Open Explorer with 2 accounts
2. On both sessions, go to test scene `/goto pejo.dcl.eth/0,0`
3. Keep one account far from the doors
4. Move the second account around the doors — doors should open on both sessions
5. Teleport the walking account to another location
6. From the remaining account, observe that the doors stay stuck in the open state

### Expected Result
`onTriggerExit` should fire when a user disconnects or teleports out of the trigger area, returning the trigger to its exited state.

### Actual Result with evidence
Doors (or any trigger-driven interaction) remain stuck in the triggered/open state after the other user leaves the scene. `onTriggerExit` callback is never called.

https://github.com/user-attachments/assets/7c67d19a-dcaf-4252-b789-9247384f6381

### Reproduction
100% — Always

### Operative system and additional Notes
Tested on Mac

### Related Issues
- #7662 — [QA] SDK Triggers | Trigger areas glitch with multiple users simultaneously

---
Requested by Ani Albano via Slack