[K/N] Turn on optimistic escape analysis

For new MM (with tracing GC), it is safe to turn it on

kotlin-native/backend.native/compiler/ir/backend.native/src/org/jetbrains/kotlin/backend/konan/llvm/IrToBitcode.kt

@@ -1710,7 +1710,8 @@ internal class CodeGeneratorVisitor(
 
     private fun needLifetimeConstraintsCheck(valueToAssign: LLVMValueRef, irClass: IrClass): Boolean {
         // TODO: Likely, we don't need isFrozen check here at all.
-        return functionGenerationContext.isObjectType(valueToAssign.type) && !irClass.isFrozen(context)
+        return context.config.memoryModel != MemoryModel.EXPERIMENTAL
+                && functionGenerationContext.isObjectType(valueToAssign.type) && !irClass.isFrozen(context)
     }
 
     private fun isZeroConstValue(value: IrExpression): Boolean {

kotlin-native/backend.native/compiler/ir/backend.native/src/org/jetbrains/kotlin/backend/konan/optimizations/EscapeAnalysis.kt

@@ -1812,10 +1812,7 @@ internal object EscapeAnalysis {
             val intraproceduralAnalysisResult =
                     IntraproceduralAnalysis(context, moduleDFG, externalModulesDFG, callGraph).analyze()
             InterproceduralAnalysis(context, generationState, callGraph, intraproceduralAnalysisResult, externalModulesDFG, lifetimes,
-                    // TODO: This is a bit conservative, but for more aggressive option some support from runtime is
+                    propagateExiledToHeapObjects = context.config.memoryModel != MemoryModel.EXPERIMENTAL
-                    // needed (namely, determining that a pointer is from the stack; this is easy for x86 or x64,
-                    //         but what about all other platforms?).
-                    propagateExiledToHeapObjects = true
             ).analyze()
         } catch (t: Throwable) {
             val extraUserInfo =