[sambsnyd]

AddJaxbRuntime hands its dependency changes to four other recipes. Each of those needs a scan pass first, but this recipe called them without one, so they always ran with no scan data. As a result, versions held in properties of other files were never updated:

• Maven: when the runtime's version is a property in an in-repo parent POM (com.sun.xml.bind:jaxb-impl:${jaxb.version}), the dependency was renamed to org.glassfish.jaxb:jaxb-runtime, but the parent property stayed at the old version. The upgrade to 2.3.x was silently skipped.
• Gradle: when the version is in gradle.properties or an ext variable, the dependency was renamed but kept the old version, and the variable was never raised to 2.3.x.

If the old version was never published under the new coordinates, both cases broke the build.

These recipes now scan along with AddJaxbRuntime, so property-based versions are upgraded alongside the rename. A side effect is that the rename and upgrade now also apply to Kotlin build scripts (build.gradle.kts).

Affects every migration that includes jaxb-apis.yml: Java 11+, Jakarta EE and Spring Boot.

New tests in AddJaxbRuntimeTest cover the Maven parent-property and gradle.properties cases.