[Fix] iOS build error: No type or protocol named OSLiveActivities

[shepherd-l]

Description

One Line Summary

Fixes iOS build error: No type or protocol named 'OSLiveActivities'

Details

Motivation

Fixes Unity iOS builds

Scope

The Unity iOS plugin bridge files require the following imports instead of being included in OneSignalFramework. OneSignalCore import was added due to LiveActivities being moved into a module in the native OneSignal iOS SDK in version 5.2.0. The swift version of the OneSignalOSCore import seems to be needed due C++ and Objective-C translation. The same issue and fix was also done previously for OSUser.

Testing

Manual testing

Tested OneSignal initialization, app build with Unity 2021.3.10f1 of the OneSignal example App on an iPhone 12 with iOS 15.5.

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