Implement new assert semantics in back-end

Previously, assert was just a regular function and its argument used to
be computed on each call (even if assertions are disabled on JVM).
This change adds support for 3 new behaviours of assert:
* always-enable (independently from -ea on JVM)
* always-disable (independently from -ea JVM)
* runtime/jvm (compile the calls like javac generates assert-operator)
* legacy (leave current eager semantics) - this already existed

Default behaviour is legacy for now.

The behavior is changed based on -Xassertions flag.
 #KT-7540: Fixed

compiler/testData/codegen/box/assert/alwaysDisable.kt

@@ -0,0 +1,40 @@
+// IGNORE_BACKEND: JS
+// KOTLIN_CONFIGURATION_FLAGS: ASSERTIONS_MODE=always-disable
+// WITH_RUNTIME
+
+fun checkTrue(): Boolean {
+    var hit = false
+    val l = { hit = true; true }
+    assert(l())
+    return hit
+}
+
+fun checkTrueWithMessage(): Boolean {
+    var hit = false
+    val l = { hit = true; true }
+    assert(l()) { "BOOYA!" }
+    return hit
+}
+
+fun checkFalse(): Boolean {
+    var hit = false
+    val l = { hit = true; false }
+    assert(l())
+    return hit
+}
+
+fun checkFalseWithMessage(): Boolean {
+    var hit = false
+    val l = { hit = true; false }
+    assert(l()) { "BOOYA!" }
+    return hit
+}
+
+fun box(): String {
+    if (checkTrue()) return "FAIL 0"
+    if (checkTrueWithMessage()) return "FAIL 1"
+    if (checkFalse()) return "FAIL 2"
+    if (checkFalseWithMessage()) return "FAIL 3"
+
+    return "OK"
+}