Fix race: let RYW-aware IAM fetches bypass the rate limiter

When resolveConditionsWithID resolves a stale IamFetchReadyCondition("")
with null before the onModelUpdated coroutine registers its condition,
the null-rywData fetch wins the rate limiter and blocks the subsequent
RYW-consistent fetch for 30s. Skip the rate-limit check when rywData is
non-null so the RYW fetch always proceeds.

Made-with: Cursor

Author: nan-li

OneSignalSDK/onesignal/in-app-messages/src/main/java/com/onesignal/inAppMessages/internal/InAppMessagesManager.kt

@@ -296,7 +296,6 @@ internal class InAppMessagesManager(
         }
     }
 
-    // called when a new push subscription is added, or the app id is updated, or a new session starts
     private suspend fun fetchMessages(rywData: RywData?) {
         // We only want to fetch IAMs if we know the app is in the
         // foreground, as we don't want to do this for background
@@ -321,7 +320,7 @@ internal class InAppMessagesManager(
 
         fetchIAMMutex.withLock {
             val now = _time.currentTimeMillis
-            if (lastTimeFetchedIAMs != null && (now - lastTimeFetchedIAMs!!) < _configModelStore.model.fetchIAMMinInterval) {
+            if (rywData == null && lastTimeFetchedIAMs != null && (now - lastTimeFetchedIAMs!!) < _configModelStore.model.fetchIAMMinInterval) {
                 return
             }