Crash: EXC_BAD_ACCESS in HelpshiftX 10.4.1

**Description**
Since releasing our latest version on **February 10th**, where we have updated HelpShiftX to `10.4.1`, we have encountered this crash **82 times** in production (and it's growing). It seems to be related to HelpshiftX’s user management (`HsUserManager removeUserLifecycleDelegate`). The crash appears to happen when trying to remove an item from `NSConcreteHashTable`, possibly due to an invalid reference.

**Stack Trace**
```
EXC_BAD_ACCESS: Attempted to dereference garbage pointer 0x62390c70b9aae0.

0 libobjc.A.dylib +0x3c20 _objc_msgSend
1 Foundation +0xdfd4 _hashProbe
2 Foundation +0xfa1c -[NSConcreteHashTable removeItem:]
3 HelpshiftX +0x20f88 __45-[HsUserManager removeUserLifecycleDelegate:]_block_invoke
4 libdispatch.dylib +0x236c __dispatch_call_block_and_release
5 libdispatch.dylib +0x40cc __dispatch_client_callout
6 libdispatch.dylib +0xb6d4 __dispatch_lane_serial_drain
7 libdispatch.dylib +0xc1dc __dispatch_lane_invoke
8 libdispatch.dylib +0x17254 __dispatch_root_queue_drain_deferred_wlh
9 libdispatch.dylib +0x16aa0 __dispatch_workloop_worker_thread
10 libsystem_pthread.dylib +0x4c78 __pthread_wqthread
```

**Environment Details**
- **Helpshift SDK Version:** `10.4.1`
- **iOS Version:** `iOS 18.1.1`
- **App Version:** `4.0.20`
- **Device Model:** `iPhone12,3`
- **Crash Occurrence:** 82 times since release

**Steps to Reproduce (if known)**
We do not have exact reproduction steps, but the crash is happening when Helpshift’s user lifecycle delegate is removed (`HsUserManager removeUserLifecycleDelegate`). It could be related to improper object lifecycle management or an issue with Helpshift's internal user management.

**Expected Behavior**
The SDK should safely handle user delegate removal without causing crashes due to invalid memory access.

**Additional Context**
This crash is affecting production users and seems to be triggered during Helpshift lifecycle management. If you need additional logs or specific device details, let me know.

Would appreciate any guidance on resolving or mitigating this issue. Thanks!