chore: Update wire-apps-jvm-sdk version to 0.2.0

[bbaarriiss]

Update wire-apps-jvm-sdk to 0.2.0 (previous was 0.2.0-alpha)

[spoonman01]

LGTM

[claude]

Code Review

Thanks for the update! This is a clean, minimal change — bumping wire-apps-jvm-sdk from 0.2.0-alpha to the stable 0.2.0 release. Moving off a pre-release dependency is good hygiene. A few notes:

Code quality — The diff is a single, focused, well-scoped change with a clear commit message. Nothing to flag stylistically.

Potential issues to verify

• API compatibility: The codebase consumes a fair amount of the SDK surface (WireAppSdk, WireEventsHandlerSuspending, WireException, WireMessage, Conversation, ConversationMember, QualifiedId, WireApplicationManager). Alpha-to-stable transitions sometimes carry breaking changes (renamed/removed symbols, signature tweaks). The main safeguard here is that the build still compiles and tests pass — please confirm the CI build is green on this PR before merging.
• Behavioral changes / changelog: If the SDK has release notes for 0.2.0, it is worth a quick skim for behavioral changes (e.g. MLS/E2EE handling) that are not surfaced at compile time but could affect runtime.
• Reproducibility: 0.2.0 is an immutable published artifact (vs. a moving alpha), which is a nice improvement for build reproducibility.

Performance & Security — No direct performance or security impact from the change itself. If the new SDK version includes security fixes over the alpha, that is a point in favor of merging.

Test coverage — No test changes are needed for a version bump, but the existing suite passing is what gives confidence this upgrade is safe. The SDK is exercised by UserCommunicationServiceTest, SetupTest, and the Stub helpers — make sure those run cleanly against 0.2.0.

Verdict: LGTM assuming CI is green. The only real risk is an unnoticed API/behavior change from the alpha, which a passing build + test run will confirm.