Android device only receive 1 notification when offline.

My app sends non-collapsible push notification.
When push notification are sent while device is online, everything works fine. Notifications are sent one by one. The problem is that if the device is offline (closed or airplane mode) only the last notification sent is received when the device come back online.

A work around that seems to be popular online is to generate unique collapseKey to force firebase to push notification in separate "collapse group".
I know the limit is only 4 collapse key, but it is enough notifications for the app I'm building.

I've achieved the desired result on IOS by settings my apns-collapse-id to a random UUID for each notifications but now that I'me trying with android it doesn't seems to work.

I uses
Firebase-admin version 9.1.1
```

com.google.firebase
firebase-admin
9.1.1

```
This library uses FCM HTTP v1 endpoint

The collapseKey fields works.
When setting it with this function : `AndroidConfig.builder().setCollapseKey("non_unique_collapse_key").build()`

The notifications are overwritten.

If I set it like this : `AndroidConfig.builder().setCollapseKey(UUID.randomUUID().toString()).build()`

All notification are sent separately.

The problem is that if I put my android to airplane mode, send myself 3 notifications (with 3 different collapse_key)
When I put my device back online, I only receive the last notification sent.

The same cannot be said for IOS.

I set my notification like so :
```
ApnsConfig.builder().putHeader("apns-collapse-id", collapseKey)
.setAps(Aps.builder().setAlert(
ApsAlert.builder().setTitle(title).setBody(notificationContent).build()).build())
.build();
```

and when I put my iphone back online, I receive 3 notifications.

Comienza con el uso de AndroidConfig.builder().setCollapseKey y la configuración de Firebase Admin Java SDK 9.1.1 descrita en la issue. Reproduce el comportamiento con un dispositivo Android en modo avión, enviando tres notificaciones con claves de colapso distintas a través del endpoint FCM HTTP v1, y compara el resultado con la configuración de APNs. El trabajo estará terminado cuando determines si el comportamiento de entrega de Android es el esperado o identifiques un problema documentado del SDK o de FCM.

Escrito por el modelo de indexación a partir del texto del issue.