Write test case for compilation ordering bug

[wmdietl]

#1536 was a tricky issue to debug. Seemingly out of nowhere, Ubuntu 24.04 CI runs started failing. Downgrading to Ubuntu 22.04 fixed it.

#1558 finally fixed the issue, by handling PARAMETER and TYPE_PARAMETER elements when finding the corresponding source code.
#1558 unfortunately did not fix the issue.

Copilot reasoned that the order of compilation must have changed between these two versions of Ubuntu and that this inconsistent handling of two elements resulted in the incompatible type.

It would be nice to confirm this and have a reproducible test case, using jtreg, where we control the compilation order. (See

checker-framework/checker/jtreg/issue1133/Main.java

Line 6 in 4c32fa9

* @compile/fail/ref=errorAB.out -XDrawDiagnostics -processor org.checkerframework.checker.nullness.NullnessChecker ClassA.java ClassB.java

for an example.)

Look at the error message in #1536. Look at the involved classes. Look at whether one is @AnnotatedFor and the other is not. Write minimal test classes that reproduce the failure before #1558 and ensure the error is fixed after #1558.

[wmdietl]

Well, #1558 still didn't fix the issue :-(

01df2e1 might be a good starting point to write test cases.
Do simplify the names and properly integrate the build.

[wmdietl]

#1563 tries considering the GATF annotated, to avoid the ordering issue.