[Feat] Add Android 13 push permission prompting

[nan-li]

Description

One Line Summary

This PR implements push permission prompting in Android for Android 13 devices.

Details

Motivation

This is a new Android 13 features/requirement.

Scope

Push permission prompting on Android 13 devices. In order to not immediately be prompted in Android 13, apps will need to set their Android target SDK version to 33+.

Pre-existing OneSignal.PromptForPushNotificationsWithUserResponse method has the following changes:

• Works on Android
• Added an optional fallbackToSettings option.

promptForPushNotificationsWithUserResponse(fallbackToSettings?: boolean, handler?: (response: boolean) => void)

Testing

Manual testing

I tested on physical iPhone 13 and Android emulator on API 33 using combinations of allowing, denying, changing the permission in settings, and re-prompting. These are the ways of calling the method tested.

OneSignal.promptForPushNotificationsWithUserResponse();

OneSignal.promptForPushNotificationsWithUserResponse(true);

OneSignal.promptForPushNotificationsWithUserResponse(false);

OneSignal.promptForPushNotificationsWithUserResponse(res => console.log(res));

OneSignal.promptForPushNotificationsWithUserResponse(undefined, (res) => console.log(res));

OneSignal.promptForPushNotificationsWithUserResponse(true, (res) => console.log(res));

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
  • Prompting
• 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 

[jkasten2]

Looks good to me, just one nit, if that is addressed can merge without anther approval.

Reviewed 8 of 8 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @kesheshyan and @nan-li)

---

src/index.ts line 186 at r1 (raw file):

        if (!isNativeModuleLoaded(RNOneSignal)) return;

        var fallbackToSettings = false;

nit, should use let instead of var.