[Fix] Request permission for notifications on Android when permission is true

[shepherd-l]

Description

One Line Summary

Resolves notification request permission on Android when notification permission is true.

Details

Motivation

Calling OneSignal.Notificaitons.RequestPermissionAsync() on Android does not return when notification permission is true and awaits forever.

Scope

Issue on wrappers that use Java bridge code. A check has to be added whereas on the native Android SDK, Kotlin resolves this automatically.

Testing

Manual testing

Tested OneSignal.Notificaitons.RequestPermissionAsync() returns true when notification permission is granted, app build with Unity 2021.3.10f1 of the OneSignal example App on a Pixel 6 with Android 13.

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 

[jkasten2]

This sounds like a bug with our OneSignal-Android-SDK that should be fixed instead, so we don't have to work around it in all our wrapper SDKs.

Can you reproduce the continuation not firing when using the OneSignal-Android-SDK with Java code in a native Android app?

[shepherd-l]

I may have been butchered the explanation but I talked about it with @nan-li here: OneSignal/OneSignal-Flutter-SDK#806 (comment)

I can try to reproduce it though

[shepherd-l]

Closing due to work on fixing this in the OneSignal Android SDK instead