chore(deps): update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.9.0

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.jetbrains.kotlinx:kotlinx-serialization-json	1.7.3 -> 1.9.0

---

Release Notes

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

v1.9.0

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

This release updates Kotlin version to 2.2.0, includes several bugfixes and provides serializers for kotlin.time.Instant.

Add kotlin.time.Instant serializers

Instant class was moved from kotlinx-datetime library to Kotlin standard library.
As a result, kotlinx-datetime 0.7.0 no longer has serializers for the Instant class.
To use new kotlin.time.Instant class in your @​Serializable classes,
you can use this 1.9.0 kotlinx-serialization version (Kotlin 2.2 is required).
You can choose between default InstantSerializer which uses its string representation,
or specify InstantComponentSerializer that represents instant as its components.
See details in the PR.

Other bugfixes

• Fix resize in JsonPath (#​2995)
• Fixed proguard rules for obfuscation to work correctly (#​2983)

v1.8.1

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

This release updates Kotlin version to 2.1.20, while also providing several important improvements
and bugfixes.

Improvements

• Implemented encoding null in key and value of a map in Protobuf (#​2910)
• Make type argument in JsonTransformingSerializer nullable (#​2911)
• Use SPDX identifier in POMs (#​2936) (thanks to Leon Linhart)
• Add watchosDeviceArm64 to Okio integration module (#​2920) (thanks to Daniel Santiago)
• Update kotlinx-io version to 0.6.0 (#​2933) (thanks to Piotr Krzemiński)

Bugfixes

• Fix incorrect enum coercion during deserialization from JsonElement (#​2962)
• Supply proper equals(), hashCode(), and toString() for SerialDescriptor() wrapper (#​2942)
• Do not encode empty packed collections in protobuf (#​2907)

v1.8.0

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

This release contains all of the changes from 1.8.0-RC. Kotlin 2.1.0 is used as a default, while upcoming 2.1.10 is also supported.
Also added small bugfixes, including speedup of ProtoWireType.from (#​2879).

---

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 this update again.

---

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

---

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

[github-actions]

Qodana Community for JVM

46 new problems were found

Inspection name	Severity	Problems
'Enum.values()' is recommended to be replaced by 'Enum.entries' since 1.9	🔶 Warning	14
Inconsistent comment for Java parameter	🔶 Warning	6
Unstable API Usage	🔶 Warning	6
Unused symbol	🔶 Warning	2
Redundant semicolon	🔶 Warning	1
Explicit 'get' or 'set' call	◽️ Notice	9
Return or assignment can be lifted out	◽️ Notice	4
If-Null return/break/... foldable to '?:'	◽️ Notice	1
Redundant empty primary constructor	◽️ Notice	1
Unnecessary '@OptIn' annotation	◽️ Notice	1
Accessor call that can be replaced with property access syntax	◽️ Notice	1

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions