Fix the failed Android release: unpin Robolectric's SDK, re-cut as android-v0.11.4

[Shik3i]

The android-v0.11.3 release build failed at the Unit tests step — every Robolectric test in core:data threw UnsupportedOperationException before running. My regression, from #23.

What happened

To let a test assert the German notification strings are actually translated, I enabled merged resources for unit tests. That made Robolectric derive its SDK from the merged manifest, which targets API 37, and it refused (targetSdkVersion=37 > maxSdkVersion=36). I pinned sdk=36 in a robolectric.properties.

That passed locally and could never pass in CI: I am on JDK 21, the release workflow is on JDK 17, and the API 36 android-all image needs the newer JVM. So a string assertion ended up tying every test in the module to the relationship between the app's targetSdk and the build's JDK.

It also slipped past the PR: by design, check-release-policy keeps Android builds out of every workflow except android-release.yml, so PR CI never runs these tests. The mitigation is running both release-workflow tasks locally before tagging — which I hadn't.

The fix

The two failure modes worth guarding are a key that was never translated and a placeholder set that disagrees between locales. Both are visible in the resource XML, so the test reads it directly — no merged resources, no SDK pin, no Android runtime. core/data/build.gradle.kts goes back to what it was and robolectric.properties is gone.

Verification

• Injected the original regression (German new_episodes_title left as the English string) → the test fails.
• Restored → passes.
• ./gradlew --no-daemon testDebugUnitTest testReleaseUnitTest, both tasks the release workflow runs: BUILD SUCCESSFUL, 93 tests in core:data, 0 failures.

v0.11.5 (Docker) released successfully and is unaffected. No GitHub Release or artifact was produced for android-v0.11.3, so nothing downstream consumed that tag.

🤖 Generated with Claude Code

[Shik3i]

Version bumped to versionCode 44 / versionName 0.11.4 on your call — android-v0.11.3 stays as a failed tag that published nothing, and its number is retired rather than reused.

Re-verified after the bump: testDebugUnitTest + testReleaseUnitTest both green, :app:assembleDebug builds, release-policy check passes.

Note for reviewers: no CI runs on this PR. ci.yml only triggers on apps/web/**, services/api/**, packages/openapi/** and the build files — this change is Android-only, and check-release-policy deliberately keeps Android builds out of every workflow except android-release.yml. The tag push is the first time CI will exercise it.