Update compose compiler version for kotlin 1.9.24

[eymar]

This fixes https://youtrack.jetbrains.com/issue/CMP-1612 and https://youtrack.jetbrains.com/issue/CMP-1602/Html-js-error-content-is-not-a-function

[igordmn]

We still have a crash on Kotlin 1.9.23 and Kotlin 2.0.0. How difficult it will be to maintain backward compatibility with these Kotlin's?

Alternatively:

• For 1.9.23 we need to release a new Compiler (not sure if it worth it).
• For Kotlin 2.0.0 we can decide that it should be updated to a hotfix version of Kotlin 2.0.10

[eymar]

We still have a crash on Kotlin 1.9.23 and Kotlin 2.0.0. How difficult it will be to maintain backward compatibility with these Kotlin's?

Alternatively:
For 1.9.23 we need to release a new Compiler (not sure if it worth it).
For Kotlin 2.0.0 we can decide that it should be updated to a hotfix version of Kotlin 2.0.10

• For 1.9.23 it's up to us to publish a compiler plugin with a fix. (Probably we don't need to do that, as everyone can use 1.9.24)
• For 2.0.0, since it's already published, the only way to make 1.7.0- compatible with 2.0.0 is to remove a newly added function in compose runtime (web). Compose compiler (2.0.0) looks for that function, and if it's present, it starts using it (the problem is that 2.0.0 Compose compiler, the web pieces "don't know" about the new function).

IMO, removing the function for only 1 platform is not a future-proof solution, because this way the platforms behaviour might diverge and it might cause other issues.
Suggesting users to switch to 2.0.10 is the best solution IMO, especially considering the Alpha status of CfW.

P.S. The multiplatform compose compiler tests (WIP) will likely prevent such a situation in the future (if they will be running on the latest compose-runtime).

[igordmn]

Suggesting users to switch to 2.0.10 is the best solution IMO, especially considering the Alpha status of CfW.

Agree, I didn't take Alpha status into account.