fix(messaging, android): repair crash handling remote notifications

WritableNativeMap has a check to see if it is consumed or not when it is used,
to prevent resolving a Promise in native code then attempting to modify it.

We may use the same WritableNativeMap object twice though when handling deferred
initial notifications. Crash repair is to store a copy so the Maps are distinct

Author: mikehardy

packages/messaging/android/src/main/java/io/invertase/firebase/messaging/ReactNativeFirebaseMessagingModule.java

@@ -83,7 +83,7 @@ public void getInitialNotification(Promise promise) {
             } else {
               remoteMessageMap = ReactNativeFirebaseMessagingSerializer.remoteMessageToWritableMap(remoteMessage);
             }
-            if (remoteMessageMap != null){
+            if (remoteMessageMap != null) {
               promise.resolve(remoteMessageMap);
               initialNotificationMap.put(messageId, true);
               return;
@@ -228,9 +228,10 @@ public void onNewIntent(Intent intent) {
         } else {
           remoteMessageMap = ReactNativeFirebaseMessagingSerializer.remoteMessageToWritableMap(remoteMessage);
         }
-        
-        if (remoteMessageMap != null){
-          initialNotification = remoteMessageMap;
+
+        if (remoteMessageMap != null) {
+          // WritableNativeMap not be consumed twice. But it is resolved in future and in event below. Make a copy - issue #5231
+          initialNotification = remoteMessageMap.copy();
           ReactNativeFirebaseMessagingReceiver.notifications.remove(messageId);
 
           ReactNativeFirebaseEventEmitter emitter = ReactNativeFirebaseEventEmitter.getSharedInstance();