KT-36336 @EnhancedNullability and null checks

Don't insert implicit null check on a value of @EnhancedNullability type
used where @EnhancedNullability type is expected.

This uncovers a bunch of other problems in FE and BE.
KT-36343 and KT-36347 are bugs in StrictJavaNullabilityAssertions
implementation which should most likely be fixed in next major language
version (with proper breaking change notice).
KT-36344 is a design problem which should be addressed after 1.4 issues
are resolved.

compiler/testData/codegen/box/ranges/javaInterop/javaArrayOfInheritedNotNullFailFast.kt

@@ -1,13 +1,16 @@
 // !LANGUAGE: +StrictJavaNullabilityAssertions
 // TARGET_BACKEND: JVM
 // IGNORE_BACKEND_FIR: JVM_IR
-// IGNORE_BACKEND: JVM
+// IGNORE_BACKEND: JVM, JVM_IR
 // WITH_RUNTIME
 
 // Note: This fails on JVM (non-IR) with "Fail: should throw on get() in loop header". The not-null assertion is not generated when
 // assigning to the loop variable. The root cause seems to be that the loop variable is a KtParameter and
 // CodegenAnnotatingVisitor/RuntimeAssertionsOnDeclarationBodyChecker do not analyze the need for not-null assertions on KtParameters.
 
+// Note: this fails on JVM_IR because of KT-36343.
+// It requires potentially breaking changes in FE, so please, don't touch it until the language design decision.
+
 // FILE: box.kt
 import kotlin.test.*