Add support for Kotlin K2 compiler plugin

[markushi]

📜 Description

As of now:

• tests are broken, seems to be some configuration/version issue with the compiletesting library

DEFAULT
java.lang.NoSuchFieldError: DEFAULT
	at com.tschuchort.compiletesting.KotlinCompilation.<init>(KotlinCompilation.kt:143)
	at io.sentry.compose.JetpackComposeInstrumentationTest$Fixture.compileFile(JetpackComposeInstrumentationTest.kt:83)

• when plugin is applied, it no-ops with the following error. This seems to stem from some compiler side API changes, it's probably best to peek into the JPC plugin source and align with their way of doing it.

w: No definition of androidx.compose.ui.Modifier found, Sentry Kotlin Compiler plugin won't run. Please ensure you're applying to plugin to a compose-enabled project.

💡 Motivation and Context

Support K2, fixes #698

💚 How did you test it?

📝 Checklist

• I reviewed the submitted code
• I added tests to verify the changes
• I updated the docs if needed
• No breaking changes

🔮 Next steps

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 4f92f66

[romtsn]

there's a better maintained fork of kotlin-comple-testing, maybe we should try that one? https://github.com/ZacSweers/kotlin-compile-testing

[markushi]

there's a better maintained fork of kotlin-comple-testing, maybe we should try that one? ZacSweers/kotlin-compile-testing

Yeah I tried, but unfortunately that fork suffers from the same limitation:

Because the internal APIs of the Kotlin compiler often change between versions, we can only support one kotlin-compiler-embeddable version at a time.
(link)

[romtsn]

LGTM, good stuff! I assume it's still backward-compatible with older kotlin compiler versions, right?

[romtsn]

looks like the test is failing because we're still running against an older kotlin version. Should we introduce another dimension to the matrix for kotlin versions?

[markushi]

looks like the test is failing because we're still running against an older kotlin version. Should we introduce another dimension to the matrix for kotlin versions?

Yeah I tried to do that, but upgrading to Kotlin 2.0 breaks in several areas:

• kapt breaks in the android-instrumentation-sample example
• the -Xjvm-default=enable flag is not supported in 2.0 anymore

Hate to say it, but I'll create a follow up ticket for this. In the meantime I tested this change with different Kotlin versions locally.