[expo-notifications][Android] Get notification responses when app in background or not running

[douglowder]

Why

After the Android notifications change to FCMv1, the app is not able to get notification response listeners to fire when the app is in background or not running, and opened in response to a notification.

How

This change leverages the Expo module Android lifecycle listeners to get the notification data from the lifecycle methods, and pass them to the notification emitter that emits notifications and responses to JS.

This change also includes support for the useLastNotificationResponse() hook. This is especially important if the app is not running and is opened in response to a notification, since response listeners may not become active early enough in initial render.

Fixes #14078 .

Test Plan

• CI should pass
• Testing with release builds of an Android app on real devices

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[linear]

ENG-12137 [Android] NotificationResponseReceivedListener not called when app is killed

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: 4a28d5b

Fingerprint diff

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

---

Generated by PR labeler 🤖

[douglowder]

Fix for #28883 has been published. Pick up latest expo package (51.0.7) and do npx expo install --fix to pick up expo-notifications 0.28.2. You will also get a new version of expo-dev-client that fixes an unnecessary reload issue on Android (see #28893).

[BrodaNoel]

Are these console.log ok?