[5.0.0] no functional changes - jsonRepresentation method name consistency

[nan-li]

Description

One Line Summary

All public objects that need a serialization method for wrapper SDKs have one, but make the method naming consistent by using jsonRepresentation for all.

Details

Motivation

• All public objects that need a serialization method for wrapper SDKs have one
• But some are named toDictionary while the majority are named jsonRepresentation
• For consistency, name all these to jsonRepresentation

Checked all of these objects:

✅ OSInAppMessage 
✅ OSInAppMessageAction 
✅ OSOutcomeEvent 
✅ OSPushSubscriptionState 
✅ OSPushSubscriptionStateChanges 
✅ OSPermissionState
✅ OSPermissionStateChanges 
✅ OSNotification 
✅ OSNotificationOpenedResult 

I don't think I am missing any other public objects.

Scope

Nit naming.

Testing

Manual testing

Dev app builds and runs.

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