[expo-notifications][Android] Fix FCMv1 icons and NPE

[douglowder]

Why

• Fixes Push Notification Icon not working on Android #24844
• Corrects an NPE that can happen if a deep link in the app is opened

How

• Change constants in the expo-notifications plugin to the correct ones expected for FCMv1
• Add the recommended code to guard against NPE when logging Android lifecycle events

Test Plan

• CI should pass
• Test app should show the correct icon and color in notification banners

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-12395 Fix notification icons on Android with FCMv1

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: 2838b79

Fingerprint diff

[
  {
    "type": "file",
    "filePath": "../../packages/expo-notifications/plugin/build/withNotificationsAndroid.js",
    "reasons": [
      "expoConfigPlugins"
    ],
    "hash": "7631970262a7128665478596c766d12b49b1da5a"
  },
  {
    "type": "dir",
    "filePath": "../../packages/expo-notifications/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "ace590ae951e514059650b7d06b90f1fd27f54fe"
  }
]

---

Generated by PR labeler 🤖

[douglowder]

Published in expo-notifications 0.28.5

[mlukasik-dev]

@douglowder, @christopherwalter,
The release did not resolve the NPE issue. It still occurs when a user opens an app link.

Although I'm not a Java developer, I am curious about how using Objects.requireNonNull would solve this issue.
From my understanding, this method throws a [customized] exception when the value is null.

[douglowder]

@mlukasik-dev thanks for the report. I will get the NPE fixed in the next two days. Sorry for my confusion about that API.

[douglowder]

@mlukasik-dev NPE is fixed in #29370 and published in expo-notifications@0.28.6

[mlukasik-dev]

That was quick. Thank you very much! I can confirm that the issue has been resolved and deep links are working correctly on Android.