FIR: introduce separate companion object resolve context

Before this commit, during the resolve of companion objects we used
the same context than for any nested class. However, during companion
object resolve we should not have companion object receiver itself
accessible in any case (in particular, it should not be accessible
in constructor). So in this commit we introduced separate context
for this purpose.

compiler/testData/codegen/box/objects/selfReferenceToCompanionObjectInInlineLambdaInSuperConstructorCall.kt

@@ -1,4 +1,3 @@
-// IGNORE_BACKEND_FIR: JVM_IR
 abstract class Base(val fn: () -> String)
 
 class Host {

compiler/testData/codegen/box/objects/selfReferenceToInterfaceCompanionObjectInInlineLambdaInSuperConstructorCall.kt

@@ -1,4 +1,3 @@
-// IGNORE_BACKEND_FIR: JVM_IR
 abstract class Base(val fn: () -> String)
 
 interface Host {

compiler/testData/diagnostics/tests/scopes/classHeader/companionObjectSuperConstructorArguments.fir.kt

@@ -1,19 +0,0 @@
-open class S(val a: Any, val b: Any, val c: Any) {}
-
-interface A {
-    companion object : S(prop1, prop2, func()) {
-        val prop1 = 1
-        val prop2: Int
-            get() = 1
-        fun func() {}
-    }
-}
-
-class B {
-    companion object : S(prop1, prop2, func()) {
-        val prop1 = 1
-        val prop2: Int
-            get() = 1
-        fun func() {}
-    }
-}

compiler/testData/diagnostics/tests/scopes/classHeader/companionObjectSuperConstructorArguments.kt

@@ -1,3 +1,4 @@
+// FIR_IDENTICAL
 open class S(val a: Any, val b: Any, val c: Any) {}
 
 interface A {