[CFG] Fix var initialization check of nested lambdas and trys

In deeply nested cases of a try-finally within a lambda, local var
initialization checks can report false positives due to the recent
capture-by-value changes meant for local val initialization checks.

^KT-70133 Fixed

compiler/fir/checkers/src/org/jetbrains/kotlin/fir/analysis/cfa/util/PropertyInitializationInfoCollector.kt

@@ -93,13 +93,6 @@ class PropertyInitializationInfoCollector(
         data: PathAwarePropertyInitializationInfo
     ): PathAwarePropertyInitializationInfo {
         val result = super.visitEdge(from, to, metadata, data)
-        if (metadata.label == CapturedByValue) {
-            // Remove properties from data that are not captured by value.
-            val invalidProperties = data.flatMapTo(hashSetOf()) { it.value.keys }.filter { !it.isCapturedByValue }
-            return invalidProperties.fold(result) { filteredData, symbol ->
-                filteredData.removeRange(symbol)
-            }
-        }
         if (!metadata.kind.isBack) return result
         val declaredVariableSymbolsInCapturedScope = when {
             from is PostponedLambdaExitNode -> declaredVariablesInLoop[from.fir.anonymousFunction]

compiler/testData/diagnostics/tests/controlFlowAnalysis/nestedTryFinallyLambda.kt

@@ -0,0 +1,43 @@
+// FIR_IDENTICAL
+fun invokeLater(x: () -> Unit) {
+    x()
+}
+
+fun nestedFinallyAndLambda1() {
+    var x: String
+    invokeLater {
+        x = ""
+        invokeLater {
+            try {
+            } finally {
+                x.length
+            }
+        }
+    }
+}
+
+fun nestedFinallyAndLambda2() {
+    var x: String
+    invokeLater {
+        x = ""
+        try {
+        } finally {
+            invokeLater {
+                x.length
+            }
+        }
+    }
+}
+
+fun nestedFinallyAndLambda3() {
+    var x: String
+    try {
+    } finally {
+        invokeLater {
+            x = ""
+            invokeLater {
+                x.length
+            }
+        }
+    }
+}