[FIR] Refactor effective visibility calculation

Before this commit, we had effective visibility as a part of FIR status,
so it was integrated into the full pipeline. In this commit,
we introduced "effective visibility as a service" which is now used
only by exposed visibility checker. This allows us to make the thing
universal for all FIR nodes, including nodes for Java / deserialized.

compiler/testData/diagnostics/tests/cyclicHierarchy/javaKotlinJavaCycle.fir.kt

@@ -6,7 +6,7 @@ interface A extends C {
 
 // FILE: B.kt
 
-interface B : A {
+interface B : <!EXPOSED_SUPER_INTERFACE!>A<!> {
     fun bar()
 }
 

compiler/testData/diagnostics/tests/cyclicHierarchy/kotlinJavaCycle.fir.kt

@@ -6,6 +6,6 @@ class J extends K {
 
 // FILE: K.kt
 
-class K : J() {
+class K : <!EXPOSED_SUPER_CLASS!>J<!>() {
     fun bar() {}
 }

compiler/testData/diagnostics/tests/cyclicHierarchy/kotlinJavaKotlinCycle.fir.kt

@@ -12,6 +12,6 @@ class J extends I {
 
 // FILE: K.kt
 
-open class K : J() {
+open class K : <!EXPOSED_SUPER_CLASS!>J<!>() {
     fun baz() {}
 }

compiler/testData/diagnostics/tests/cyclicHierarchy/kotlinJavaNestedCycle.fir.kt

@@ -1,6 +1,6 @@
 // FILE: ExceptionTracker.kt
 
-interface ExceptionTracker : LockBasedStorageManager.ExceptionHandlingStrategy {
+interface ExceptionTracker : <!EXPOSED_SUPER_INTERFACE!>LockBasedStorageManager.ExceptionHandlingStrategy<!> {
 }
 
 // FILE: StorageManager.kt