[FIR] fix resolution ambiguities between weakly compatible expect and actual

There is a corresponding example inside the stdlib,
see `kotlin.text.startsWith`.

JVM and common counterpart are weakly-compatible
as the actual declaration has default arguments,
which results in `ExpectActualCompatibility.Incompatible.ActualFunctionWithDefaultParameters`

This commit allows such cases.

^KT-61732 fixed

core/compiler.common/src/org/jetbrains/kotlin/resolve/multiplatform/ExpectActualCompatibility.kt

@@ -99,6 +99,10 @@ sealed class ExpectActualCompatibility<out D> {
     object Compatible : ExpectActualCompatibility<Nothing>()
 }
 
+val ExpectActualCompatibility<*>.isCompatibleOrWeaklyIncompatible: Boolean
+    get() = this is ExpectActualCompatibility.Compatible
+            || this is ExpectActualCompatibility.Incompatible.WeakIncompatible
+
 val ExpectActualCompatibility<*>.compatible: Boolean
     get() = this == ExpectActualCompatibility.Compatible