[KUP] Disable opt-in Kotlin compiler warnings

[FenstonSingel]

It was decided to deprecate and phase out the concept (see KT-77721).

[FenstonSingel]

IDK what the problem with the TC build is.
It doesn't seem to be related to these changes given that it's reproducible for the master branch, though.

[fzhinkin]

IDK what the problem with the TC build is.
It doesn't seem to be related to these changes given that it's reproducible for the master branch, though.

There are two problems:

• WasmJs compilation fails due to missing opt-in (Opt-in ExperimentalWasmJsInterop annotation #319)
• Native compilation fails for some reason (and I can't reproduce the failure outside CI)

[FenstonSingel]

There are two problems:

• WasmJs compilation fails due to missing opt-in (Opt-in ExperimentalWasmJsInterop annotation #319)
• Native compilation fails for some reason (and I can't reproduce the failure outside CI)

@woainikk The divergence between this public TC configuration and our internal KUP TC configuration (which, AFAICT, has been green for a while now and didn't surface any of these problems) looks like a potential issue.

[woainikk]

The kotlin-community/dev and master in benchmarks have differences, so the configs may also differ

[FenstonSingel]

The kotlin-community/dev and master in benchmarks have differences, so the configs may also differ

AFAICT, the only effective difference is 89fde29, and this difference is accounted for in the public TC configuration by passing -Pmin_supported_gradle_version=7.6.3 via the command line. So IDK, it still seems suspicious that our internal configuration is silent.

[fzhinkin]

Native compilation fails for some reason (and I can't reproduce the failure outside CI)

It seems to be induced by Linux-only K/N builds we're using in a corresponding CI task. I disabled cross-compilation for that task and filed #320 to enable it back later.