[expo-notifications][Android] Add default channel plugin prop, restore legacy icon and color

[douglowder]

Why

Based on customer feedback from expo-notifications@0.28.7, three adjustments are still needed:

• Set both FCM legacy and FCMv1 metadata items in the Android manifest, so that icon and color work in both cases
• Add a config plugin property, defaultChannel, to allow a developer to set the FCMv1 default channel in the manifest.
• The Android lifecycle listeners should check to see if the intent extras have a notificationResponse object, and not map the intent bundle to create a duplicate response in JS.

See this comment by @mgscreativa and other comments in that issue.

How

• Make the appropriate code changes in the plugin and in ExpoNotificationLifecycleListener.java

Test Plan

• CI should pass
• Test app patched with these changes should behave as expected

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-12457 Clean up notifications plugin properties and code for icon, color, default channel

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: 81cdcee

Fingerprint diff

[
  {
    "type": "file",
    "filePath": "../../packages/expo-notifications/plugin/build/withNotificationsAndroid.js",
    "reasons": [
      "expoConfigPlugins"
    ],
    "hash": "8852a43319643083dce105dd17a0d7fde531531a"
  },
  {
    "type": "dir",
    "filePath": "../../packages/expo-notifications/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "047f6878c85fe0f7d43f9373eb0235f419acea8d"
  }
]

---

Generated by PR labeler 🤖

[douglowder]

@amandeepmittal @Simek this will be cherry-picked to SDK 51, do I need to also make doc changes manually in docs/pages/versions/v51.0.0?

[amandeepmittal]

... this will be cherry-picked to SDK 51, do I need to also make doc changes manually in docs/pages/versions/v51.0.0?

@doug, the data file (.json) for SDK 51 needs to be generated to apply changes to the SDK 51 API reference.

[douglowder]

@amandeepmittal this doc change is not in the generated API .json file, it is in the manually written notifications.mdx page.

[amandeepmittal]

@amandeepmittal this doc change is not in the generated API .json file, it is in the manually written notifications.mdx page.

My bad, I assumed this was generated from the package source (as with other packages are 😅 ) and forgot this one isn't. I'll create a follow-up PR to apply the doc changes to SDK 51 reference page too, in a while.