Support for custom serializer

[yoobi]

Description

PR is related to issue: #178

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Enhancement (Improves existing functionality)

IMPORTANT: By submitting a patch, you agree to allow the project
owners to license your work under the terms of
the Apache License 2.0.

[github-actions]

Hey there! Thank you for this PR :) Please take a moment to review our community guidelines to make the contribution process easy and effective for everyone involved.

[yoobi]

There is also a possiblity of non-breaking change for user who use the EmojiInitializer.

Inside the lib AndroidManifest:

<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    android:exported="false"
    tools:node="merge">
    <meta-data
        android:name="io.wax911.emojify.initializer.EmojiInitializer"
        android:value="androidx.startup" />
</provider>

If user is using custom Deserializer
Inside the user AndroidManifest:

<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    android:exported="false"
    tools:node="merge">
    <meta-data
        android:name="com.package.CustomEmojiInitializer"
        android:value="androidx.startup" />
    <meta-data
        android:name="io.wax911.emojify.initializer.EmojiInitializer"
        android:value="androidx.startup"
        tools:node="remove" />
</provider>

[wax911]

Please run ./gradlew :emojify:spotlessCheck to check for any formatting issues and ./gradlew :emojify:spotlessApply to apply auto fixable

[yoobi]

Sure ! It is done :)

I've noticed that you've tagged this changed as breaking but it is not

[wax911]

Sure ! It is done :)

I've noticed that you've tagged this changed as breaking but it is not

Oh, I had seen this #178 (comment) thus the breaking status

[yoobi]

Yes at first it was a breaking change, but I've refacto the code in order to change it as non-breaking. I've explained in this comment

[wax911]

The PR looks solid, I just have one concern though, since the property annotation on the Model class are for kotlinx.serialization unless we make an interface/abstraction for the model and allow users to implement it and provide annotation for deserialization which we can substitute with the interface for usage. Otherwise some of the json property names don't automatically match the model property names. What are your thoughts?

[yoobi]

I have made a couple test with MoshiDeserializer (I have made a CustomDeserializer in the app example so users could experiment with it) and even though there was no Moshi annotation on the Emoji model it did find the right data for supports_fitzpatrick and supports_gender. I could try with Gson or Jackson to make sure if we need to abstract the model or not

[yoobi]

So I've added implementation for Jackson and Gson and they do work fine without the need to expose the Model.
I've made a change in the first emoji to try it out and they did return "true" for supports_fitzpatrick and supports_gender

[wax911]

Perfect, this is amazing! Could we just rename AEmojiInitializer to AbstractEmojiInitializer

[github-actions]

Auto approved automated PR

[yoobi]

Hello ! I'm back with bad news :'(
I have tried to implement the new version in my project and it seems what we feared (#179 (comment)) is true and kotlinx-serialization is still needed