Add getters and observer for onesignal ID and external ID

[jennantilla]

Description

One Line Summary

Add getters for onesignal ID and external ID, and a user state observer to know when these values are changed.

Details

Motivation

From developer feedback and to support integration partners, we are exposing the onesignal ID and external ID with getters.

We also want to grant developers the ability to add observers that can be called when there is a change in user state.

Testing

Manual testing

Manually tested on:

• Pixel 7 Pro Emulator running Android 14
• iPhone 15 Pro running iOS 17.0.1

Tested adding observer for user state and calling new methods to access externalId and onesignalId. Ensured congruency between iOS and Android responses.

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 

[nan-li]

I'm having trouble running and testing, so these are just comments while I am not able to run the app

[jennantilla]

@nan-li I Successfully reran these test scenarios on Android 14 Emulator and iOS 17.2 Emulator:

1. New app install, call getters for onesignal ID and external ID and see they are null.

 LOG  OneSignal Id:  null
 LOG  External Id:  null

2. Observer fires once the onesignal ID is received

LOG  OneSignal: user changed: {"current":{"externalId":null,"onesignalId":"b6c0868f-d166-45bf-8844-85b4e02d251e"}}

3. Observer fires after calling login

LOG  OneSignal: user changed: {"current":{"externalId":"jma222","onesignalId":"0debeb54-c62c-487c-a276-39c680bc64bc"}}

[nan-li]

Not a blocker, avoid using android.util.Log - since it looks like we are using that a lot already, we can refactor in the future.
The reason is similar to this PR done for ios: OneSignal/OneSignal-iOS-SDK#1219

[jennantilla]

Thanks for flagging! Refactoring will happen in a future PR.