Use Roboelectric to make some tests (especially mappers) unit tests instead of instrumented tests

[rfc2822]

No description provided.

[Copilot]

Pull Request Overview

Migrates Android tests to Robolectric-based unit tests to improve test execution speed and development workflow. The PR replaces instrumented tests with unit tests that can run on the JVM using Robolectric for Android framework mocking.

Key changes:

• Added Robolectric dependency and test runner configuration to all test classes
• Migrated tests from androidTest to test directory structure
• Updated imports to use explicit references instead of wildcard imports
• Modified build configuration to support Robolectric unit tests

Reviewed Changes

Copilot reviewed 39 out of 52 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
lib/build.gradle.kts	Added Robolectric dependency and enabled Android resources for unit tests
gradle/libs.versions.toml	Added Robolectric version definition
lib/src/test/kotlin/at/bitfire/vcard4android/contactrow/*.kt	Added @RunWith(RobolectricTestRunner::class) annotations and import cleanup
lib/src/test/kotlin/at/bitfire/synctools/**/*.kt	Converted tests to use Robolectric with proper imports
lib/src/test/kotlin/at/bitfire/ical4android/**/*.kt	Migrated various utility and core tests to Robolectric
lib/src/androidTest/kotlin/at/bitfire/ical4android/Css3ColorTest.kt	Moved from androidTest to test directory

Comments suppressed due to low confidence (1)

lib/src/test/kotlin/at/bitfire/ical4android/LocaleNonWesternDigitsTest.kt:47

• Using String.Companion.format is unnecessarily verbose. Use String.format directly as it's a static method.

        Assert.assertEquals("2020", String.Companion.format(Locale.ROOT, "%d", 2020))