[IR] Split const folding into necessary one and for optimizations only

In this commit we have a lot of change in test data. This was caused
by the way where we evaluate constants. We split constant evaluation
into two distinct parts: only necessary evaluations for `fir2ir`
(like const val and annotations) and optimizations for lowering.
Now we don't do all constant evaluation on `fir2ir`, but IR
dump is executed after this phase, so test data changed.

#KT-58923

compiler/testData/codegen/box/involvesIrInterpreter/jsFloatDoubleToString.kt

@@ -1,5 +1,7 @@
 // TARGET_BACKEND: JS_IR
 // IGNORE_BACKEND_K1: JS_IR, JS_IR_ES6
+// IGNORE_BACKEND_K2: JS_IR, JS_IR_ES6
+// TODO enable for K2 when const lowering is applied for js 
 fun <T> T.id() = this
 
 const val toStringDouble1 = 1.0.<!EVALUATED("1")!>toString()<!>