The Jakarta annotation migration adds jakarta.annotation-api for imports the parser could not resolve

[jkschneider]

Java 8 also ships javax.annotation.Resource and the other Common Annotations, so Java 8 LSTs leave them unresolved too, and JavaxAnnotationMigrationToJakartaAnnotation moved @Resource to jakarta.annotation.Resource without adding jakarta.annotation-api. It now runs AddApiDependencyForImports, the #1257 recipe as generalized in the previous pull request, for jakarta.annotation and 2.0.x. Imports from javax.annotation.processing, which is still in the JDK, and javax.annotation.concurrent, which comes from JSR-305, do not count, the same packages the migration's non-recursive ChangePackage already leaves alone.

Found by a team of coding agents reviewing a Moderne run of org.openrewrite.java.migrate.jakarta.JavaxMigrationToJakarta over the 31 Arquillian repositories (run 20261003120559-YQoma). The issue is annotation-api-missing-java8 in the run's io.moderne.RecipeIssues data table (1 row), and the fix was discussed and reviewed on the run's message board. A row from the table, as a generalized example:

Java 8 Resource annotations are migrated without adding their Jakarta API. (arquillian/arquillian-rusheye, rusheye-api/pom.xml, recipe org.openrewrite.java.migrate.jakarta.JavaxMigrationToJakarta)

Before:

No annotation dependency; class A { @javax.annotation.Resource Object value; }

What the recipe produced:

No annotation dependency; class A { @jakarta.annotation.Resource Object value; }

Expected:

jakarta.annotation:jakarta.annotation-api:2.0.0; class A { @jakarta.annotation.Resource Object value; }

Stacked on #1264 (2 of 19); merge that one first.