[notifications][android] Add methods to request schedule exact permission

[behenate]

Why

As of Android 14, SCHEDULE_EXACT_ALARM is denied by default.

This permission is needed for scheduleNotificationAsync to work at an exact time. Without this permission, the notification will still trigger, but it the time will be approximate.

ENG-11673

How

Added appropriate methods to the NotificationPermissions module. This permission requires launching an intent for a result.

Unfortunately when user selects allow and then disallows right away android restarts the app after closing the intent. This causes react to crash, because it tries to deliver intent result to non-existing delegate. I'm still looking for a solution for this problem.

The docs still need to be finished

Test Plan

Tested in BareExpo in Android 14

[expo-bot]

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Missing changelog entries

Your changes should be noted in the changelog. Read Updating Changelogs guide and consider adding an appropriate entry to the following changelogs:

• packages/expo-notifications/CHANGELOG.md

---

Generated by ExpoBot 🤖 against 532d2ba

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: 202f26a

Fingerprint diff

[
  {
    "type": "dir",
    "filePath": "../../packages/expo-notifications/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "4f7df154ac3b8ccf29db2fc6f06843d251cc4d78"
  }
]

---

Generated by PR labeler 🤖