Bump OneSignal Android and iOS SDKs

[shepherd-l]

Description

One Line Summary

Updates included OneSignal Android SDK from 5.1.17 to 5.1.20 and OneSignal iOS SDK from 5.2.2 to 5.2.3

Details

Motivation

Applies fixes made in the native SDKs to the Unity wrapper SDK.

Scope

• Updated included Android SDK from 5.1.17 to 5.1.20
  • Optimized the initialization process by moving some service initialization to a background thread
  • Recover null onesignal ID crashes for Operations
  • Add option to default to HMS over FCM
  • Prevent retrying IAM display if 410 is received from backend
  • Fix dynamic triggers showing IAM repeatedly after being dismissed
  • For full changes, see the native release notes
• Updated included iOS SDK from 5.2.2 to 5.2.3
  • The user executor needs to uncache first which fixes some cached requests being dropped for past users
  • Omit misleading fatal-level log for cross-platform SDKs
  • For full changes, see the native release notes

Testing

Manual testing

Tested OneSignal initialization, app build with Unity 2022.3.10f1 of the OneSignal example app on a emulated Pixel 4 with Android 12 and a physical iPhone 12 with iOS 17.5.1.

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is