JVM IR: output stable ABI binaries by default

#KT-43592 Fixed

compiler/testData/cli/jvm/abiStabilityIncorrectValue.args

@@ -0,0 +1,5 @@
+$TESTDATA_DIR$/simple.kt
+-d
+$TEMP_DIR$
+-Xuse-ir
+-Xabi-stability=unknown

compiler/testData/cli/jvm/abiStabilityIncorrectValue.out

@@ -0,0 +1,2 @@
+error: unknown ABI stability mode: unknown, supported modes: [stable, unstable]
+COMPILATION_ERROR

compiler/testData/cli/jvm/abiStabilityUnstableWithOldBackend.args

@@ -0,0 +1,4 @@
+$TESTDATA_DIR$/simple.kt
+-d
+$TEMP_DIR$
+-Xabi-stability=unstable

compiler/testData/cli/jvm/abiStabilityUnstableWithOldBackend.out

@@ -0,0 +1,2 @@
+error: -Xabi-stability=unstable is not supported in the old JVM backend
+COMPILATION_ERROR

compiler/testData/cli/jvm/extraHelp.out

@@ -1,9 +1,10 @@
 Usage: kotlinc-jvm <options> <source files>
 where advanced options include:
   -Xabi-stability={stable|unstable}
-                             When using unstable compiler features such as FIR or JVM IR, use 'stable' to mark generated class files as stable
+                             When using unstable compiler features such as FIR, use 'stable' to mark generated class files as stable
                              to prevent diagnostics from stable compilers at the call site.
-
+                             When using the JVM IR backend, conversely, use 'unstable' to mark generated class files as unstable
+                             to force diagnostics to be reported.
   -Xadd-modules=<module[,]>  Root modules to resolve in addition to the initial modules,
                              or all modules on the module path if <module> is ALL-MODULE-PATH
   -Xallow-no-source-files    Allow no source files