Update high level components to be accessed via pascal case

[brismithers]

Description

One Line Summary

Update high level components to be accessed via pascal casing.

Details

Motivation

To keep consistent, make all high level components accessible via a property that is in pascal case (i.e. OneSignal.Notifications, OneSignal.InAppMessages, etc). This is in contradiction to Kotlin best practices, but is favored to keep access patterns consistent across the SDK.

Scope

This is name change only, no functional changes.

Testing

Manual testing

No testing was performed. The codebase compiles, and existing unit tests pass.

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 

[iAmWillShepherd]

LGTM!

[jkasten2]

Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @emawby, @jennantilla, @nan-li, and @shepherd-l)