test: migrate jvmTest suites to commonTest across 17 modules (B2 — 74 files, 936 tests)

[pkmetski]

Background

Follow-up to #1073 (partially closed by #1088 and pkmetski/issue-1073-verify-impl).

Category B2 from the parity backlog: 74 jvmTest files across 17 modules contain ~936 @Test functions that run only on the JVM. For modules that already target iOS (e.g. feature:*, core:common, core:models, core:domain, core:sources, core:sync), tests with pure-Kotlin logic should move to commonTest so they execute on iosSimulatorArm64Test in CI.

Scope

Affected modules (approximate — a full audit needed):
core:common, core:models, core:domain, core:net, core:sources, core:sync, feature:library, feature:source, feature:reader, and others.

Per-file blockers follow the same pattern as B1:

• JVM-only APIs (String.format, java.net.URLEncoder, java.text.Normalizer, etc.) — need expect/actual or shared replacement
• Backtick names with (, ), or , — rename + Removed-test: trailer

Why it's a separate issue

74 changed files across 17 modules far exceeds the ~50-file single-PR guideline.

Acceptance criteria

• Every eligible jvmTest in iOS-targeted modules has a commonTest counterpart
• Remaining jvmTest files carry Parity-skip: trailers
• All touched module iosSimulatorArm64Test tasks green
• ./gradlew test jvmTest riffleChecks green