The Jakarta Validation migration upgrades Hibernate Validator to 7.0

[jkschneider]

Hibernate Validator before 7 registers a javax.validation.spi.ValidationProvider, so after the migration jakarta.validation.Validation.buildDefaultValidatorFactory() finds no provider. JavaxValidationMigrationToJakartaValidation now changes the old org.hibernate:hibernate-validator coordinates to org.hibernate.validator:hibernate-validator 7.0.x and upgrades existing org.hibernate.validator dependencies to 7.0.x, the Jakarta Validation 3 line, keeping their scope. Hibernate Validator 7 also needs a Jakarta Expression Language implementation for standalone bootstrap, which this does not add.

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 hibernate-validator-javax-provider-retained 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:

Jakarta Validation bootstrap retains a javax-only Hibernate Validator provider. (arquillian/continuous-enterprise-development, code/application/pom.xml, recipe org.openrewrite.java.migrate.jakarta.JavaxMigrationToJakarta)

Before:

org.hibernate:hibernate-validator:4.3.0.Final; javax.validation.Validation.buildDefaultValidatorFactory();

What the recipe produced:

org.hibernate:hibernate-validator:4.3.0.Final; jakarta.validation.Validation.buildDefaultValidatorFactory();

Expected:

org.hibernate.validator:hibernate-validator:7.0.5.Final; org.glassfish:jakarta.el:4.0.2; jakarta.validation.Validation.buildDefaultValidatorFactory();

Stacked on #1276 (14 of 19); merge that one first.