The Jakarta migration updates Jakarta EE type names in string literals

[jkschneider]

ChangePackage moves imports but leaves class names in string literals, so code that looks types up by name, such as Arquillian's test enrichers checking for "javax.inject.Inject" or "javax.ejb.EJB", or that writes a services/javax.enterprise.inject.spi.Extension descriptor, silently stopped finding the migrated APIs. New declarative recipe JavaxRuntimeTypeNamesToJakarta, run early in JavaxMigrationToJakarta, applies ChangePackageInStringLiteral to javax.inject, javax.enterprise, javax.ejb and javax.servlet, and ChangeTypeInStringLiteral to javax.annotation.Resource and javax.annotation.Resources. It is limited to those names on purpose, so strings naming Java SE packages that stay in javax, such as javax.annotation.processing, javax.naming, javax.net.ssl and javax.transaction.xa, are left 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 issues are javax-reflective-names-retained in the run's io.moderne.RecipeIssues data table (21 rows) and cdi-service-path-literal-retained (2 rows), and the fix was discussed and reviewed on the run's message board. A row from the table, as a generalized example:

Unmigrated runtime class names disable Jakarta availability checks or annotation recognition. (arquillian/arquillian-core, testenrichers/cdi/src/main/java/org/jboss/arquillian/testenricher/cdi/CDIInjectionEnricher.java, recipe org.openrewrite.java.migrate.jakarta.JavaxMigrationToJakarta)

Before:

class A { String type = "javax.inject.Inject"; }

What the recipe produced:

class A { String type = "javax.inject.Inject"; }

Expected:

class A { String type = "jakarta.inject.Inject"; }

Stacked on #1270 (8 of 19); merge that one first.