use LockTimeoutException instead of PessimisticLockException on Postgres and h2

this is perhaps not *perfectly* correct for Postgres, but I believe it's good
enough for our purposes (this error code can occur in some other situations,
but they are very unlikely to affect us, it seems to me)

Author: gavinking

hibernate-core/src/main/java/org/hibernate/dialect/H2Dialect.java

@@ -15,7 +15,6 @@
 import java.util.TimeZone;
 
 import org.checkerframework.checker.nullness.qual.Nullable;
-import org.hibernate.PessimisticLockException;
 import org.hibernate.QueryTimeoutException;
 import org.hibernate.boot.model.FunctionContributions;
 import org.hibernate.boot.model.TypeContributions;
@@ -38,6 +37,7 @@
 import org.hibernate.exception.ConstraintViolationException;
 import org.hibernate.exception.ConstraintViolationException.ConstraintKind;
 import org.hibernate.exception.LockAcquisitionException;
+import org.hibernate.exception.LockTimeoutException;
 import org.hibernate.exception.spi.SQLExceptionConversionDelegate;
 import org.hibernate.exception.spi.TemplatedViolatedConstraintNameExtractor;
 import org.hibernate.exception.spi.ViolatedConstraintNameExtractor;
@@ -810,7 +810,7 @@ public SQLExceptionConversionDelegate buildSQLExceptionConversionDelegate() {
 							new LockAcquisitionException(message, sqlException, sql);
 					case 50200 ->
 						// LOCK NOT AVAILABLE
-							new PessimisticLockException(message, sqlException, sql);
+							new LockTimeoutException(message, sqlException, sql);
 					case 23505 ->
 						// Unique index or primary key violation
 							new ConstraintViolationException( message, sqlException, sql, ConstraintKind.UNIQUE,
@@ -828,6 +828,7 @@ public SQLExceptionConversionDelegate buildSQLExceptionConversionDelegate() {
 							new ConstraintViolationException( message, sqlException, sql, ConstraintKind.CHECK,
 									getViolatedConstraintNameExtractor().extractConstraintName( sqlException ) );
 					case 57014 ->
+						// QUERY CANCELLED
 							new QueryTimeoutException( message, sqlException, sql );
 					default -> null;
 				};

hibernate-core/src/main/java/org/hibernate/dialect/PostgreSQLDialect.java

@@ -21,7 +21,6 @@
 import org.hibernate.Length;
 import org.hibernate.LockMode;
 import org.hibernate.LockOptions;
-import org.hibernate.PessimisticLockException;
 import org.hibernate.QueryTimeoutException;
 import org.hibernate.boot.model.FunctionContributions;
 import org.hibernate.boot.model.TypeContributions;
@@ -46,6 +45,7 @@
 import org.hibernate.engine.jdbc.env.spi.NameQualifierSupport;
 import org.hibernate.engine.spi.SessionFactoryImplementor;
 import org.hibernate.exception.LockAcquisitionException;
+import org.hibernate.exception.LockTimeoutException;
 import org.hibernate.exception.spi.SQLExceptionConversionDelegate;
 import org.hibernate.exception.spi.TemplatedViolatedConstraintNameExtractor;
 import org.hibernate.exception.spi.ViolatedConstraintNameExtractor;
@@ -1041,13 +1041,13 @@ public SQLExceptionConversionDelegate buildSQLExceptionConversionDelegate() {
 			final String sqlState = extractSqlState( sqlException );
 			if ( sqlState != null ) {
 				switch ( sqlState ) {
-					case "40P01":
-						// DEADLOCK DETECTED
+					case "40P01": // DEADLOCK DETECTED
 						return new LockAcquisitionException( message, sqlException, sql );
-					case "55P03":
-						// LOCK NOT AVAILABLE
-						return new PessimisticLockException( message, sqlException, sql );
-					case "57014":
+					case "55P03": // LOCK NOT AVAILABLE
+						//TODO: should we check that the message is "canceling statement due to lock timeout"
+						//      and return LockAcquisitionException if it is not?
+						return new LockTimeoutException( message, sqlException, sql );
+					case "57014": // QUERY CANCELLED
 						return new QueryTimeoutException( message, sqlException, sql );
 				}
 			}