HHH-19846 - Drop JUnit 4 usage: correction to ManipulationCriteriaTest (that somehow slipped through the maze)

Signed-off-by: Jan Schatteman <jschatte@redhat.com>

Author: jrenaat

hibernate-core/src/test/java/org/hibernate/orm/test/jpa/criteria/ManipulationCriteriaTest.java

@@ -11,6 +11,7 @@
 import jakarta.persistence.criteria.Root;
 import jakarta.persistence.criteria.Subquery;
 
+import org.hibernate.cfg.JpaComplianceSettings;
 import org.hibernate.dialect.MySQLDialect;
 import org.hibernate.orm.test.jpa.metamodel.Address;
 import org.hibernate.orm.test.jpa.metamodel.Alias;
@@ -26,6 +27,7 @@
 import org.hibernate.testing.orm.junit.EntityManagerFactoryScope;
 import org.hibernate.testing.orm.junit.JiraKey;
 import org.hibernate.testing.orm.junit.Jpa;
+import org.hibernate.testing.orm.junit.Setting;
 import org.hibernate.testing.orm.junit.SkipForDialect;
 
 import org.junit.jupiter.api.AfterEach;
@@ -41,7 +43,7 @@
 @Jpa(
 		annotatedClasses = {Customer.class, Address.class, Alias.class, CreditCard.class, Order.class, LineItem.class,
 				Product.class, Spouse.class, Info.class, Phone.class},
-		queryComplianceEnabled = true
+		integrationSettings = {@Setting(name = JpaComplianceSettings.JPA_QUERY_COMPLIANCE, value = "true")}
 )
 public class ManipulationCriteriaTest {