Bump kotlinx.collections.immutable to 0.5.0-beta01

[DmitryNekrasov]

Summary

Bumps kotlinx.collections.immutable from 0.4.0 to 0.5.0-beta01.

0.5.0-beta01 is binary-compatible with 0.4.0 — per KEEP-0459, the copy-returning methods on Persistent* types were renamed (e.g. add → adding, remove → removing), and the old names remain as @Deprecated(WARNING) overloads. So this PR is purely a version bump and is reversible.

Why no source changes?

element-x-android uses kotlinx.collections.immutable as a read-only consumer — persistentListOf(...) etc. as factories, with values typed everywhere as ImmutableList<T> / ImmutableMap<K, V> / ImmutableSet<T> (the read-only interfaces). None of the renamed methods on Persistent* are visible at any call site, so the Kotlin compiler emits zero kotlinx.collections.immutable deprecation warnings after the bump.

Scope checks:

• 463 .kt files import the library; 12 build files depend on it.
• 0 declarations typed as Persistent(List|Map|Set|Collection)<…>.
• 0 classes/objects/interfaces implementing the persistent interfaces.
• 0 Java callers.
• The single .mutate { } call (in IncomingVerificationStateMachine.kt) is a state-machine helper, not the kotlinx extension.

Changes

• gradle/libs.versions.toml: kotlinx_collections_immutable = "…:0.4.0" → "…:0.5.0-beta01".
• MIGRATION_REPORT.md: per-phase audit (happy to drop this if you'd prefer to keep the repo root tidy).

References

• Upstream 0.5.0-MIGRATION.md
• Library #232 / #233

Test plan

• Full compile: :app (Gplay + Fdroid debug, main + UnitTest) plus compileDebugUnitTestKotlin across all ~200 subprojects — BUILD SUCCESSFUL in 4m 58s (4939 tasks), zero kotlinx.collections.immutable deprecation warnings.
• Unit tests: :libraries:recentemojis:impl:testDebugUnitTest, :libraries:usersearch:impl:testDebugUnitTest, :features:roomcall:impl:testDebugUnitTest — all pass.

🤖 Generated with Claude Code

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Thank you for your contribution! Here are a few things to check in the PR to ensure it's reviewed as quickly as possible:

• If your pull request adds a feature or modifies the UI, this should have an equivalent pull request in the Element X iOS repo unless it only affects an Android-only behaviour or is behind a disabled feature flag, since we need parity in both clients to consider a feature done. It will also need to be approved by our product and design teams before being merged, so it's usually a good idea to discuss the changes in a Github issue first and then start working on them once the approach has been validated.
• Your branch should be based on origin/develop, at least when it was created.
• The title of the PR will be used for release notes, so it needs to describe the change visible to the user.
• The test pass locally running ./gradlew test.
• The code quality check suite pass locally running ./gradlew runQualityChecks.
• If you modified anything related to the UI, including previews, you'll have to run the Record screenshots GH action in your forked repo: that will generate compatible new screenshots. However, given Github Actions limitations, it will prevent the CI from running temporarily, until you upload a new commit after that one. To do so, just pull the latest changes and push an empty commit.

[DmitryNekrasov]

Hi @ganfra — quick heads-up: this PR came out of testing a Claude Code skill I'm building for migrating Kotlin projects to kotlinx.collections.immutable 0.5.x (Kotlin/kotlin-agent-skills#45), so element-x-android was a real-world OSS testbed for a read-only consumer. No production urgency — happy to wait for the stable 0.5.0 release before merging.