Add FCM HTTP V1 service

[dragermrb]

Add service to use FCM HTTP v1 API.

According to Google (https://firebase.google.com/docs/cloud-messaging/migrate-v1)

Apps using the deprecated FCM legacy APIs for HTTP and XMPP should migrate to the HTTP v1 API at the earliest opportunity. Sending messages (including upstream messages) with those APIs was deprecated on June 20, 2023, and will be removed in June 2024.

[shaffe-fr]

Hi,
It looks like new message format is not yet implemented. Is it planned?

[matiss-zalans]

@dragermrb Thanks for the solution. We are using your fork. Just wanted to leave a comment here. I know that main project does not allow to use multiple fcm api keys with config structure, but that can be dealt with by using ->setApiKey() . Here I had a bit of a headache. When initializing FcmV1 with default configs or setting projectId the url property was updated. I was using ->setConfig() to set everything at once, that property was not updated. So just a feedback. You could add a check to update url property after setting the whole config. Was trying to find ->setUrl(), but class didn't have that, but PushService::class had that so I had to contruct the full url the same way as in your class. So another feedback. You could override ->setUrl() with project-id injection or something like that where users pass can project-id and code itself could use when reading from config or calling ->setProjectId().

[dragermrb]

Hi @matiss-zalans

I have overwritten setConfig() method to updates the URL

[pushpak1300]

Any plans to merge this ?

[hossamadelelsayed]

is this PR will be merged soon ?

[pultho]

Hi thanks for your contribution here. I will have a look at this next weeks and will prepare a release for that.

[AbdulRahmanIqbal]

how much time it will take to fix?