Upgrade Spring Boot 3 Maven parents to 3.5 in the Java 25 migration

[jkschneider]

Spring Boot 3.0 to 3.3 bundle a Spring Framework whose repackaged ASM cannot read Java 25 class files: after UpgradeToJava25 the application compiles, and its context tests fail with Unsupported class file major version 69. Three of the eight repositories in the run hit this. New composite UpgradeSpringBootParentForJava25, part of UpgradeToJava25: when the Maven parent is spring-boot-starter-parent 3.x, upgrade it to 3.5.x with UpgradeParentVersion. It stays within Boot 3 (Boot 2 needs the Jakarta migration first) and never touches Boot 4. Gradle plugin and BOM imports are not covered here.

Found by a team of coding agents reviewing a Moderne run of org.openrewrite.java.migrate.UpgradeToJava25 over eight open-source repositories (run 20261003103223-WtyA8). The issue is spring-boot-java25-bytecode in the run's io.moderne.RecipeIssues data table, and the fix was discussed and reviewed on the run's message board. A row from the table, as a generalized example:

The migration retains Spring Boot 3.0.1 whose Spring ASM cannot read Java 25 bytecode. (fhsinchy/movieist, pom.xml)

Before:

<project><parent><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter-parent</artifactId><version>3.0.1</version></parent><properties><java.version>17</java.version></properties></project>

What the recipe produced:

<project><parent><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter-parent</artifactId><version>3.0.1</version></parent><properties><java.version>25</java.version></properties></project>

Expected:

<project><parent><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter-parent</artifactId><version>3.5.16</version></parent><properties><java.version>25</java.version></properties></project>

Stacked on #1253 (5 of 9); merge that one first.