Do not use dispatch receiver type when calculating method owner

Motivation of using dispatch receiver type when calculating method owner
was discussed here: https://github.com/JetBrains/kotlin/pull/3054

However, this is incompatible with type erasure of non-reified type
parameters on inlining (which will be done in future). Consider the
code:

```
inline fun <T> f(arr:  Array<T>, p: (T) -> Int): Int = p(arr[0])
fun box() = f(arrayOf("abacaba"), String::length)
```

After inlining and erasure, the type of `arr[0]` is `Any`. Thus, when
calculating owner of `String::length` we would have `Any` instead of
`String` if we used dispatch receiver type.

Note, that this change affects bytecode instruction that invokes
method, but does not change which method is being invoked.

compiler/testData/codegen/box/controlStructures/forInIterator/uintIterator.kt

@@ -20,8 +20,10 @@ fun box(): String {
 
 // CHECK_BYTECODE_TEXT
 // JVM_IR_TEMPLATES
-// 0 java/util/Iterator.hasNext \(\)Z
+// 1 java/util/Iterator.hasNext \(\)Z
 // 0 java/util/Iterator.next \(\)Ljava/lang/Object;
-// 1 MyUIntIterator.hasNext \(\)Z
+// 0 MyUIntIterator.next \(\)Ljava/lang/Object;
+// 0 MyUIntIterator.hasNext \(\)Z
 // 1 public synthetic bridge next\(\)Ljava/lang/Object;
 // 2 MyUIntIterator.next-pVg5ArA \(\)I
+// 0 INVOKEVIRTUAL kotlin/UInt.unbox-impl \(\)I