JVM: Fix default parameter values handling

When we generate call for 'foo', we make decision about invoking
a 'foo$default' too late, after the call arguments are generated.
If 'foo' was an override, and base class (interface) was generic,
'foo' in base class could have a different Kotlin and JVM
signature, so the arguments we generated could be generated wrong
(primitive or inline class values instead of boxes, see KT-38680).
Also, we always selected first base class in supertypes list,
which caused KT-15971.

Look into resolved call and see if we should actually call
'foo$default' instead of 'foo' when determining actual callable.

Overrides can't introduce default parameter values, and
override-equivalent inherited methods with default parameters
is an error in a child class. Thus, if we are calling a class
member function with a default parameters, there should be one
and only one overridden function that has default parameter values
and overrides nothing.

compiler/testData/codegen/box/defaultArguments/function/funInTraitChain.kt

@@ -1,6 +1,3 @@
-// IGNORE_BACKEND: JVM
-// See KT-15971
-
 interface Foo {
     fun foo(a: Double = 1.0): Double
 }

compiler/testData/codegen/box/defaultArguments/function/kt15971.kt

@@ -1,5 +1,4 @@
 // IGNORE_BACKEND_FIR: JVM_IR
-// IGNORE_BACKEND: JVM
 interface Q {
     fun foo(a: Double): Double
 }

compiler/testData/codegen/box/defaultArguments/function/kt15971_2.kt

@@ -1,5 +1,4 @@
 // IGNORE_BACKEND_FIR: JVM_IR
-// IGNORE_BACKEND: JVM
 interface Q {
     fun foo(a: Double) = 0.0
 }

compiler/testData/codegen/box/defaultArguments/function/kt15971_3.kt

@@ -1,5 +1,4 @@
 // IGNORE_BACKEND_FIR: JVM_IR
-// IGNORE_BACKEND: JVM
 interface Q {
     fun foo(a: Double): Double
 }