Identify User success will hydrate OSID + EUID

* On Identify User successful, the SDK was only hydrating the OneSignal ID for past users (not the current user) and fetching the current user (which means OneSignal ID will be missing locally until that response)
* Let's hydrate both OneSignal ID and External ID for all cases so that the local state can be up to date (instead of relying on the Fetch User to hydrate back the OneSignal and External IDs)

Author: nan-li

iOS_SDK/OneSignalSDK/OneSignalUser/Source/Executors/OSUserExecutor.swift

@@ -335,6 +335,19 @@ extension OSUserExecutor {
         OneSignalCoreImpl.sharedClient().execute(request) { _ in
             removeFromQueue(request)
 
+            guard let onesignalId = request.identityModelToIdentify.onesignalId else {
+                OneSignalLog.onesignalLog(.LL_ERROR, message: "executeIdentifyUserRequest succeeded but is now missing OneSignal ID!")
+                executePendingRequests()
+                return
+            }
+
+            // Need to hydrate the identity model for current user or past user with pending requests
+            let aliases = [
+                OS_ONESIGNAL_ID: onesignalId,
+                request.aliasLabel: request.aliasId
+            ]
+            request.identityModelToUpdate.hydrate(aliases)
+
             // the anonymous user has been identified, still need to Fetch User as we cleared local data
             // Fetch the user only if its the current user
             if OneSignalUserManagerImpl.sharedInstance.isCurrentUser(request.identityModelToUpdate) {