[StefanGraeber]

When parsing type annotations on types which anner INNER_TYPEs of other classes, it is required to know the enclosing class for a correct resolution. Since type annotation parsing will happen as early as completeTypeParameters and inner classes can be referenced as bounds for type parameters of the outer class, all inner classes must know their onclosing class. The same problem arises for any other usage of the inner class in the outer, e.g.

class Outer {
    private Outer.@TypeUseAnnotation Inner someField;
    class Inner {}
}

requires in completeMembers for type annotation resolution that the Outer.Inner knows its enclosing class. Since it is not possible to reference classes declared inside a code unit, this resolution step may be incomplete when resolving type annotations.

The same list is iterated twice to avoid a behavior change. The frist list changes the return value of classes.getAllWithOuterClassesSortedBeforeInnerClasses() to include more classes. Calling that method twice causes the tests creates_new_stub_type_variables_for_type_variables_of_enclosing_classes_that_are_out_of_context in ClassFileImporterGenericClassesTest and ClassFileImporterGenericMethodSignaturesTest to fail

[schulzjo-tng]

Please fix the typos in the PR description before merging, since those can go into the merge commit. Rest looks good 👍