Update kotlinx.serialization to v1.7.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.jetbrains.kotlinx:kotlinx-serialization-json	1.7.1 -> 1.7.2
org.jetbrains.kotlinx:kotlinx-serialization-core	1.7.1 -> 1.7.2

---

Release Notes

Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)

v1.7.2

==================

This release provides several new features, including a major Cbor configuration rework.
It uses Kotlin 2.0.20 by default.

Cbor feature set for COSE compliance

This change brings a lot of features to the CBOR format, namely:

• Serial Labels — see @CborLabel annotation and preferCborLabelsOverNames flag.
• Tagging of keys and values — see encode*Tags and verify*Tags set of flags
• Definite length encoding — see useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.
• Option to globally prefer major type 2 for byte array encoding — see alwaysUseByteString flag.

Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration.
It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces in your custom serializers (see their documentation for details).

All of these features make it possible to serialize and parse COSE-compliant CBOR, for example, ISO/IEC 18013-5:2021-compliant mobile driving license data.
In case you want to make use of them, there is a predefined Cbor.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.

This functionality was contributed to us by Bernd Prünster.

Keeping generated serializers

One of the most requested features for serialization plugin was to continue to generate a serializer even if a custom one is specified for the class.
It allows using a plugin-generated serializer in a fallback or delegate strategy, accessing type structure via descriptor, using default serialization behavior in inheritors that do not use custom serializers.

Starting with this release, you can specify the @KeepGeneratedSerializer annotation on the class declaration to instruct the plugin to continue generating the serializer.
In this case, the serializer will be accessible using the .generatedSerializer() function on the class's companion object.

This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.

You can check out the examples in the documentation and in the PRs: #​2758, #​2669.

Serializer for kotlin.uuid.Uuid

Kotlin 2.0.20 added a common class to represent UUIDs in a multiplatform code.
kotlinx.serialization 1.7.2 provides a corresponding Uuid.serializer() for it, making it possible to use it in @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation.
Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.

See more details in the corresponding PR.

Other bugfixes and improvements

• Prohibited using of zero and negative field numbers in ProtoNumber (#​2766)
• Improve readability of protobuf decoding exception messages (#​2768) (thanks to xiaozhikang0916)
• docs(serializers): Fix grammatical errors (#​2779) (thanks to jamhour1g)
• Fixed VerifyError after ProGuard optimization (#​2728)
• Add wasm-wasi target to Okio integration (#​2727)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[swankjesse]

This build is failing because it’s not finding kotlin/uuid/Uuid on the build classpath. Unfortunately we use kotlinx.serialization both at runtime and at build time, and that makes some things fragile.

java.lang.NoClassDefFoundError: kotlin/uuid/Uuid
    	at kotlinx.serialization.internal.PrimitivesKt.<clinit>(Primitives.kt:20)
    	at kotlinx.serialization.descriptors.SerialDescriptorsKt.PrimitiveSerialDescriptor(SerialDescriptors.kt:91)
    	at app.cash.zipline.internal.ByteStringAsHexSerializer.<clinit>(serializers.kt:32)
    	at app.cash.zipline.ZiplineManifest$Module.write$Self$zipline(ZiplineManifest.kt:100)
    	at app.cash.zipline.ZiplineManifest$Module$$serializer.serialize(ZiplineManifest.kt:100)
    	at app.cash.zipline.ZiplineManifest$Module$$serializer.serialize(ZiplineManifest.kt:100)
    	at kotlinx.serialization.json.internal.StreamingJsonEncoder.encodeSerializableValue(StreamingJsonEncoder.kt:257)
    	at kotlinx.serialization.encoding.AbstractEncoder.encodeSerializableElement(AbstractEncoder.kt:80)
    	at kotlinx.serialization.internal.MapLikeSerializer.serialize(CollectionSerializers.kt:123)
    	at kotlinx.serialization.json.internal.StreamingJsonEncoder.encodeSerializableValue(StreamingJsonEncoder.kt:257)
    	at kotlinx.serialization.encoding.AbstractEncoder.encodeSerializableElement(AbstractEncoder.kt:80)
    	at app.cash.zipline.ZiplineManifest.write$Self$zipline(ZiplineManifest.kt:34)
    	at app.cash.zipline.ZiplineManifest$$serializer.serialize(ZiplineManifest.kt:34)
    	at app.cash.zipline.ZiplineManifest$$serializer.serialize(ZiplineManifest.kt:34)
    	at kotlinx.serialization.json.internal.StreamingJsonEncoder.encodeSerializableValue(StreamingJsonEncoder.kt:257)
    	at kotlinx.serialization.json.internal.JsonStreamsKt.encodeByWriter(JsonStreams.kt:99)
    	at kotlinx.serialization.json.Json.encodeToString(Json.kt:125)
    	at app.cash.zipline.ZiplineManifest.encodeJson(ZiplineManifest.kt:271)
    	at app.cash.zipline.gradle.ZiplineCompiler.writeManifest(ZiplineCompiler.kt:160)

[JakeWharton]

Yeah we can move it to run in a worker so we don't inherit the version of Kotlin Gradle ships. That will ensure we always get the version we declare instead of whatever old version Gradle is on.