🎉 New `kotlinx-serialization` Gradle subproject

[LVMVRQUXL]

📝 Description

We want to extract our integration with the kotlinx.serialization library from the root Gradle project to a new types-kotlinx-serialization subproject. This subproject should document clearly our consumers should use it (here's an example on another Kotlin library).

Basically, consumers should be able to configure the serialization of types from Kotools Types with minimum effort by:

1. Adding the dependency in the Gradle build script of their project. Here's an example using the Kotlin DSL in Gradle:

implementation("org.kotools:types-kotlinx-serialization:0.1.0") // The version is fictive.

2. Importing the serializers module needed from Kotools Types when configuring the serialization format. Here's an example of using all serializers from Kotools Types using the JavaScript Object Notation (JSON) format from kotlinx.serialization:

val format: StringFormat = Json { serializersModule = KotoolsTypesSerializers.all }
val encoded: String = format.encodeToString(Zero)
println(encoded) // 0
val decoded: Zero = format.decodeFromString(encoded)
println(Zero === decoded) // true

After resolving this issue, the Application Programming Interface (API) should at least provide a KotoolsTypesSerializers type with the following structure:

object KotoolsTypesSerializers {
    val all: SerializersModule
    // More specific modules...
}

✅ Checklist

• [x] 🎉 Create a new kotlinx-serialization Gradle subproject with sample test, then include it in the integration and the delivery workflows.
• [x] ✨ Add the KotoolsTypesSerializers type with documentation and dump the Application Binary Interface (ABI) of this subproject.
• [x] ✨ Add the KotoolsTypesSerializers.toString() function with documentation, tests and Kotlin code sample, then dump the Application Binary Interface (ABI) of this subproject.
• [x] ✨ Add the KotoolsTypesSerializers.zero property for serializing the Zero type as Byte, with tests, documentation and Kotlin code sample, then dump the ABI of this subproject.
• [x] ✨ Add the KotoolsTypesSerializers.all property with tests, documentation and Kotlin code sample, then dump the ABI.
• [x] 📝 Configure the multi-module documentation generation with Dokka for including this subproject and the types one in the documentation.
• [x] 📝 Create a Gradle plugin named org.kotools.types.multi-module-api-reference for configuring the API reference's generation, including this new subproject and the types one.
• [x] 📝 Document the installation of this new module in a new README file.
• [x] 📝 Add an entry for this issue in the unreleased changelog.

[LVMVRQUXL]

Instead of moving serializers to this new subproject for existing types, we will introduce new serializers in this subproject only for new types defined in the org.kotools.types package. This way, we will introduce changes incrementally without breaking the old API.

[LVMVRQUXL]

For including this new Gradle subproject in the API reference with a version selector, we need to regenerate it for each version... This is out of scope of this issue and should be done in an another one.