Feat: live activities click events

[nan-li]

Description

One Line Summary

Add click events for live activities, which requires considerable client integration.

Details

There are no APIs available to know of click events on a live activity or widget. The workaround implemented is to leverage deep linking and query params to know of a click and the associated live activity data.

Apple documentation:

When the widget or Live Activity receives an interaction, the system activates the containing app and passes the URL to onOpenURL(perform:), application:openURL:options:, or application:openURLs:, depending on the life cycle your app uses.

Motivation

Add analytics for Live Activities

Scope

• No effect unless the client uses the onesignalWidgetURL modifier.
• The SDK will modify the URL passed to the app, the client must handle.

New APIs:

Widget modifier
The onesignalWidgetURL sets the URL to open in the containing app when the user clicks the widget.

.onesignalWidgetURL(URL(string: "myapp://product/12345"), context: context)

Click tracking method
The trackClickAndReturnOriginal is used in conjunction with the onesignalWidgetURL modifier. Handle a URL opened in the app to track Live Activity clicks. Call this method from your app's URL handling code.

let originalURL = OneSignal.LiveActivities.trackClickAndReturnOriginal(url)

NSURL *originalURL = [OneSignal.LiveActivities trackClickAndReturnOriginal:url];

Testing

Unit testing

Manual testing

iPhone 13 on iOS 18.6.2

Affected code checklist

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

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 

[cstyles]

We're reusing pushopen. See this turbine PR: https://github.com/OneSignal/turbine/pull/1628

Nope, we're going to add a new handler to live-activities-http.