FIR: Rewrite visibility checking

Unbound it from implicit receiver stack as it only needs scope structure/declaration nestedness
Semantics for protected has been changed in a way it works in old FE

NB: We should report additional diagnostic in case of CallCompanionProtectedNonStatic.fir.kt
(see KT-38814)

compiler/testData/diagnostics/tests/typealias/typeAliasConstructorInSuperCall.fir.kt

@@ -3,12 +3,12 @@ open class MyBase protected constructor() {
 }
 typealias MyAlias = MyBase
 
-class MyDerived1 : <!INAPPLICABLE_CANDIDATE!>MyAlias<!>()
+class MyDerived1 : MyAlias()
 class MyDerived1a : MyBase()
 
-class MyDerived2 : <!INAPPLICABLE_CANDIDATE!>MyAlias<!>(null)
+class MyDerived2 : MyAlias(null)
 class MyDerived2a : MyBase(null)
 
 class MyDerived3 : MyAlias {
-    constructor(x: Nothing?) : <!INAPPLICABLE_CANDIDATE!>super<!>(x)
-}
+    constructor(x: Nothing?) : super(x)
+}