K2: handle type parameter vs nested class conflict in body resolve properly

This commit does two things:
- prioritize type parameter scopes against static scopes in body resolve
(effectively it's a revert of KT-58028 fix)
- consider type parameters as inapplicable callable, so during callable
resolve we can go up the tower and still resolve to static scope

This allows both KT-58028 and KT-63377 to work properly
#KT-63377 Fixed

analysis/low-level-api-fir/testData/contextCollector/innerClasses.txt

@@ -12,13 +12,13 @@ Tower Data Context:
     Element 5
         Scope: FirExplicitSimpleImportingScope
     Element 6
-        Scope: FirMemberTypeParameterScope
-            Classifiers:
-                FirTypeParameterSymbol F
-    Element 7
         Scope: FirNestedClassifierScopeImpl
             Classifiers:
                 FirRegularClassSymbol public final inner class Bar<B, Outer(F)> : R|kotlin/Any|
+    Element 7
+        Scope: FirMemberTypeParameterScope
+            Classifiers:
+                FirTypeParameterSymbol F
     Element 8
         Implicit receiver:
             FirRegularClassSymbol public final class Foo<F> : R|kotlin/Any|