Investigate using bytecode instrumentation instead of compiler plugin

[romtsn]

Description

The Kotlin compiler plugin proved to be very unstable and painful to maintain. Across the past few months we've had several incompatibility issues (mostly due to the compiler plugin API changing unexpectedly in a breaking way without any notice):

• Add support of the pre-release Kotlin versions #955
• Kotlin Compiler Plugin 5.8.0 causes build break with Kotlin 2.2.0 #941
• Provide support for kotlin 2.1.20 #864
• Plugin 5.4.0 causes build break with Kotlin 2.1.20 #868
• Plugin 5.3.0 causes build break with Kotlin 2.1.20 #856
• User interaction tracking for Compose testTag stopped working #784
• Support K2 compiler #698

We should investigate feasibility of tagging Composables through bytecode manipulation. On paper this should work just fine, but it's worth trying it out first. Potential downsides:

• This ain't going to work for KMP (but we don't support it now either)
• More complicated logic since we'd have to operate on what bytecode the compose compiler plugin produces

[linear]

GRADLE-61 Investigate using bytecode instrumentation instead of compiler plugin