[5.0.0] Support multiple IAM + Notification Lifecycle Listeners

[nan-li]

Description

One Line Summary

Support multiple IAM Lifecycle Listeners + Notification Foreground Lifecycle Listeners.

Details

Motivation

No API change, but under the hood, support adding multiple listeners that remained a TODO after these two PRs:

• [5.0.0] IAM Lifecycle Listener - API update #1257
• [5.0.0] Notification Foreground Listener - API update #1258

Scope

Letting app developers add and remove multiple listeners. When there are multiple notification foreground listeners, essentially first one wins. The first listener to call preventDefault and display will trigger these events.

In addition, added jsonRepresentation to IAM lifecycle events

• so developers can call [event jsonRepresentation]
• We only want to show the properties available on OSInAppMessage, however since OSInAppMessageInternal is a subclass of OSInAppMessage, we end up exposing the internal properties. Therefore, I renamed the method on OSInAppMessageInternal to jsonRepresentationInternal, which is used for debugging.

Testing

Manual testing

Tested on iPhone 13 device on iOS version 16.5

• Tested adding and removing multiple listeners and that they are fired.
• Tested multiple listeners being involved in the notification display, by calling display and preventDefault in various configurations.

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