[Feat] Combine user property updates for network call improvements, fix purchase bug

[nan-li]

Description

One Line Summary

Combine user property updates for network call improvements by combining these updates into one request, and fix a purchase tracking bug.

Details

This PR is best read commit by commit

1. Session time, count, purchases - these changes are not model driven and now enqueue as a Delta whereas they used to be turned into Request objects immediately
2. Updated attributed and unattributed time processors to send the session time using the changes above. They will not manage their own background tasks when the app is backgrounding. They will not manage the storage of the user's session time once that time is sent to the User module to handle (except for outcomes which is separate of the user).
3. Introduce an enum OSPropertiesSupportedProperty, that restricts the properties we allow for updating a user.
4. Actual changes to combine User Update Deltas into one request
5. Fix a bug in purchase tracking where a number is sent when the server expects a string (amount).
6. Update existing tests after the above changes and add tests.

Motivation

Reduce server load.

Scope

• Individual OSDeltas' updates are combined into one payload and request.
• Other than that, Deltas and Requests are still handled and cached the same.
• Previously, a single change was a single request.
• Now there may be more surface area for request failure with increased payload.
• Added an enum representing the user property updates that can be made (such as language, session_time, etc) and block against any unsupported ones (mostly for future-proofing).
• OSDeltas can now be created and enqueued manually, whereas in the past, they were solely driven by model changes.
• Fixed purchase tracking's price property.

Testing

Unit testing

• Updated existing unit tests to reflect combining Deltas
• Added helpers to compare requests and their payload now that the payload can hold more data
• Added a test in which various user updates are made and confirm they are sent in one payload correctly
• Added a test in Objective C to test sending purchases

Manual testing

Physical iPhone 13 on iOS 17.4

Tested session ending influences, both attributed and unattributed

• Confirmed: When app is backgrounded, session time is sent to the Operation Repo before it flushes.

Tested adding tags, purchases, and backgrounding app to get session time

• Sample request payload sent

{
  "deltas" : {
    "session_time" : 32,
    "purchases" : [
      {
        "amount" : "3.00",
        "sku" : "productSku1",
        "iso" : "EUR"
      },
      {
        "iso" : "USD",
        "sku" : "productSku2",
        "amount" : "3.05"
      }
    ]
  },
  "properties" : {
    "tags" : {
      "c" : "c",
      "g" : "g",
      "h" : "h",
      "b" : "b",
      "e" : "e",
      "d" : "d"
    }
  },
  "refresh_device_metadata" : false
}

Tested logging into users and making tags updates

• Saw they are batched together for each user

OneSignal.login(userA)
OneSignal.User.addTag(key: "a", value: "a")
OneSignal.User.addTag(key: "b", value: "b")
OneSignal.User.addTag(key: "c", value: "c")
OneSignal.login(userB)
OneSignal.User.addTag(key: "d", value: "d")

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
• 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.
• I have reviewed this PR myself, ensuring it meets each checklist item

---

This change is 

[emawby]

Reviewable status: 0 of 23 files reviewed, 2 unresolved discussions (waiting on @jennantilla, @jinliu9508, @jkasten2, @nan-li, and @shepherd-l)

---

iOS_SDK/OneSignalSDK/OneSignalUser/Source/OneSignalUserManagerImpl.swift line 559 at r1 (raw file):

    /// 
    /// - Parameter property:Expected inputs are `"session_time"`, `"session_count"`, and `"purchases"`.
    func updatePropertiesDeltas(property: String, value: Any) {

Should the property parameter be of type OSPropertySupportedProperty instead of a String to ensure a supported value is being sent? The OSPropertySupportedProperty enum could have an associated string value that we use for creating the delta

---

iOS_SDK/OneSignalSDK/OneSignalUser/Source/Executors/Support/SupportedProperty.swift line 0 at r1 (raw file):
This file name should match the enum file name and maybe shouldn't be under the executor folder since it is used by the model store listener as well.

[emawby]

LGTM! The unit tests are flaky but lets address in a different pr