K2: Fix inference from assignment in PCLA

Before this, the order of the constraints being added was incorrect

^KT-64222 Fixed

compiler/testData/diagnostics/tests/builderInference/issues/kt63841.fir.kt

@@ -27,14 +27,14 @@ fun test() {
         var variable = getTypeVariable()
         variable = TargetType()
         variable.<!UNRESOLVED_REFERENCE!>targetTypeMemberFunction<!>()
-        variable = <!ASSIGNMENT_TYPE_MISMATCH!>DifferentType()<!>
+        variable = DifferentType()
         variable.<!UNRESOLVED_REFERENCE!>targetTypeMemberFunction<!>()
         variable = TargetType()
         variable.<!UNRESOLVED_REFERENCE!>targetTypeMemberFunction<!>()
     }
     // exact type equality check — turns unexpected compile-time behavior into red code
     // considered to be non-user-reproducible code for the purposes of these tests
-    checkExactType<Buildee<Any>>(<!ARGUMENT_TYPE_MISMATCH!>anyBuildee<!>)
+    checkExactType<Buildee<Any>>(anyBuildee)
 }
 
 

compiler/testData/diagnostics/tests/builderInference/issues/kt64222.fir.kt

@@ -1,16 +0,0 @@
-// ISSUE: KT-64222
-
-interface A {
-    fun bar(): B<Int>
-}
-
-interface B<T>
-fun <E> foo(block: B<E>.() -> Unit): B<E> = TODO()
-
-class C : A {
-    private var value: B<Int>? = null
-
-    override fun <!RETURN_TYPE_MISMATCH_ON_OVERRIDE!>bar<!>() = <!NEW_INFERENCE_NO_INFORMATION_FOR_PARAMETER!>foo<!> {
-        value = this
-    }
-}

compiler/testData/diagnostics/tests/builderInference/issues/kt64222.kt

@@ -1,3 +1,4 @@
+// FIR_IDENTICAL
 // ISSUE: KT-64222
 
 interface A {