Fix possible NullPointerException under notValidOrDuplicated

[Jeasmine]

NullPointerException was happening when calling notValidOrDuplicated under an OSNotificationDataController not inited; this can occur if for some reason OSNotificationDataController got cleaned from memory, or the notification processing doesn't call initWithContext.

Task:

• Init notificationDataController if controller is null
• Add description to notValidOrDuplicated method

Fixes #1357

---

This change is 

[jkasten2]

We should be calling OneSignal.initWithContext(context) internally already which initializes notificationDataController already. We may have just missed one spot. Possibly just a Service as the app's process could have been started from directly in some rare cases.

Adding OneSignal.initWithContext(context) will end up call setupContextListeners so just adding this where needed should fix the issue. Doing this means we won't have future issues where something else could be missed.

Reviewed 3 of 3 files at r1.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @emawby)

[Jeasmine]

Yeah, I wanted to avoid searching for every place since we should have one place to handle this, the initWithContext from notification handling. I have seen that most of the notification processing passes through processBundleFromReceiver, so we might want to let that function handle the init.

I will still leave the null controller check since it will avoid future problems also, and if we have the context available, we should use it.

Reviewable status: 2 of 6 files reviewed, all discussions resolved (waiting on @emawby and @jkasten2)

[jkasten2]

Reviewed 4 of 4 files at r2.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @emawby)