fix: [SDK-4814] reduce receive-receipt dedup cache TTL to 1 day

Receipts are only enqueued when a push-delivered content update arrives,
so the device is online and sends succeed promptly; a long retry window
isn't needed. As a dedup marker, an entry only has to outlive the window
in which ActivityKit can re-emit an active activity on relaunch (~12h
max), so one day covers it with margin while bounding how much the
per-notification cache can accumulate.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: nan-li

iOS_SDK/OneSignalSDK/OneSignalLiveActivities/Source/Executors/OSLiveActivitiesExecutor.swift

@@ -115,11 +115,12 @@ class StartRequestCache: RequestCache {
 }
 
 class ReceiveReceiptsRequestCache: RequestCache {
-    // Sent receipts stay as dedup markers (not only pending retries), so re-emits after relaunch aren't re-sent.
-    static let ThreeDaysInSeconds = TimeInterval(60 * 60 * 24 * 3)
+    // Sent receipts are kept as dedup markers, so bound retention: an active activity re-emits for at most
+    // ~12h on relaunch, and updates arrive over the network, so a day covers dedup and retries without piling up.
+    static let OneDayInSeconds = TimeInterval(60 * 60 * 24)
 
     init() {
-        super.init(cacheKey: OS_LIVE_ACTIVITIES_EXECUTOR_RECEIVE_RECEIPTS_KEY, ttl: ReceiveReceiptsRequestCache.ThreeDaysInSeconds)
+        super.init(cacheKey: OS_LIVE_ACTIVITIES_EXECUTOR_RECEIVE_RECEIPTS_KEY, ttl: ReceiveReceiptsRequestCache.OneDayInSeconds)
     }
 }