JVM: enable -Xlambdas=class in some codegen tests

Most of these tests check the specific structure of lambdas when they
are generated as classes, and they start to fail once invokedynamic
lambdas are enabled by default.

compiler/testData/codegen/bytecodeText/companion/privateCompanionObjectAccessors_after.kt

@@ -1,4 +1,5 @@
 // !LANGUAGE: +ProperVisibilityForCompanionObjectInstanceField
+// LAMBDAS: CLASS
 
 class Host {
     private companion object {
@@ -8,4 +9,4 @@ class Host {
     fun test() = { foo() }
 }
 
-// 1 synthetic access\$
+// 1 synthetic access\$

compiler/testData/codegen/bytecodeText/companion/protectedCompanionObjectAccessors_after.kt

@@ -1,5 +1,5 @@
 // !LANGUAGE: +ProperVisibilityForCompanionObjectInstanceField
-
+// LAMBDAS: CLASS
 // FILE: Base.kt
 package a
 
@@ -17,4 +17,4 @@ class Host : Base() {
 }
 
 // @Host.class:
-// 1 synthetic access\$
+// 1 synthetic access\$

compiler/testData/codegen/bytecodeText/constClosureOptimization.kt

@@ -1,3 +1,5 @@
+// LAMBDAS: CLASS
+
 fun test() {
 
     fun local(){

compiler/testData/codegen/bytecodeText/inline/deleteClassOnTransformation.kt

@@ -1,3 +1,5 @@
+// LAMBDAS: CLASS
+
 fun test() {
     {
         val lam = {}

compiler/testData/codegen/bytecodeText/kt10259.kt

@@ -1,3 +1,5 @@
+// LAMBDAS: CLASS
+
 fun box(): String {
     var encl1 = "fail"
     var encl2 = "fail"

compiler/testData/codegen/bytecodeText/kt9603.kt

@@ -1,3 +1,5 @@
+// LAMBDAS: CLASS
+
 class A {
     public var prop = "O"
         private set
@@ -9,4 +11,4 @@ class A {
 }
 
 // 0 INVOKESTATIC test\/A\.access\$getProp\$0
-// 1 INVOKEVIRTUAL A\.getProp
+// 1 INVOKEVIRTUAL A\.getProp

compiler/testData/codegen/bytecodeText/outerClass/classInClinit.kt

@@ -1,3 +1,4 @@
+// LAMBDAS: CLASS
 // FILE: test.kt
 
 // This should *not* have enclosing method <clinit>. See https://youtrack.jetbrains.com/issue/KT-48754.