Traverse store-load chains for POP instructions

POP instructions can be only live usages for functional parameters,
e.g., when corresponding invoke is in dead code (KT-17591).

compiler/testData/codegen/boxInline/stackOnReturn/kt17591.kt

@@ -0,0 +1,7 @@
+// FILE: 1.kt
+inline fun alwaysOk(s: String, fn: (String) -> String): String {
+    return fn(return "OK")
+}
+
+// FILE: 2.kt
+fun box() = alwaysOk("what?") { it }

compiler/testData/codegen/boxInline/stackOnReturn/kt17591a.kt

@@ -0,0 +1,7 @@
+// FILE: 1.kt
+inline fun alwaysOk(s: String, fn: (String) -> String): String {
+    try { return fn(return "fail") } finally { fn(return "OK") }
+}
+
+// FILE: 2.kt
+fun box() = alwaysOk("what?") { it }

compiler/testData/codegen/boxInline/stackOnReturn/kt17591b.kt

@@ -0,0 +1,15 @@
+// FILE: 1.kt
+inline fun alwaysOk(s: String, fn: (String) -> String): String {
+    try {
+        throw Exception()
+    }
+    catch(e: Exception) {
+        fn(return "fail")
+    }
+    finally {
+        fn(return "OK")
+    }
+}
+
+// FILE: 2.kt
+fun box() = alwaysOk("what?") { it }