[LL FIR] introduce lazy resolve tests for type annotations

From one side to check how annotation propagation works and from another
side to cover scenarios with lazy resolution from type position as it is
a valid case of usage in Analysis API (KtFirAnnotationListForType)

^KT-63042

generators/analysis-api-generator/tests/org/jetbrains/kotlin/generators/tests/analysis/api/firLowLevel.kt

@@ -58,6 +58,30 @@ internal fun TestGroupSuite.generateFirLowLevelApiTests() {
             model("lazyResolve", pattern = TestGeneratorUtil.KTS)
         }
 
+        testClass<AbstractSourceLazyTypeAnnotationsTest> {
+            model("lazyResolveTypeAnnotations", pattern = TestGeneratorUtil.KT)
+        }
+
+        testClass<AbstractOutOfContentRootLazyTypeAnnotationsTest> {
+            model("lazyResolveTypeAnnotations", pattern = TestGeneratorUtil.KT)
+        }
+
+        testClass<AbstractScriptLazyTypeAnnotationsTest> {
+            model("lazyResolveTypeAnnotations", pattern = TestGeneratorUtil.KTS)
+        }
+
+        testClass<AbstractSourceLazyDeclarationResolveForTypeAnnotationsTest> {
+            model("lazyResolveTypeAnnotations", pattern = TestGeneratorUtil.KT)
+        }
+
+        testClass<AbstractOutOfContentRootLazyDeclarationResolveForTypeAnnotationsTest> {
+            model("lazyResolveTypeAnnotations", pattern = TestGeneratorUtil.KT)
+        }
+
+        testClass<AbstractScriptLazyDeclarationResolveForTypeAnnotationsTest> {
+            model("lazyResolveTypeAnnotations", pattern = TestGeneratorUtil.KTS)
+        }
+
         testClass<AbstractStdLibSourcesLazyDeclarationResolveTest> {
             model("lazyResolveStdlibSources")
         }