patched Java-based migration

Java-based migrations run out-of-order and can't conflict with the lastest SQL-based migrations

Author: mlm483

src/main/java/org/breedinginsight/db/migration/V1_32_0__Set_Dev_Admin_Email.java

@@ -78,8 +78,12 @@ private void addConstraint(Context context) throws SQLException {
 
         // Add new constraint
         try (Statement altTable = context.getConnection().createStatement()) {
+            // NOTE: because Java-based migrations don't run at build time, they end up running last (out of order) on
+            // application startup. If they haven't been applied to the database already. For that reason, the reference
+            // to column `orcid` was changed to `oauth_id` 2025-08-25 to allow this migration to run after
+            // V1.34.0__rename-orcid.sql.
             String sql = "ALTER TABLE bi_user\n" +
-                    "ADD CONSTRAINT " +CONSTRAINT_NAME+ " CHECK ( (email IS NOT NULL ) OR (orcid IS NULL) ) ;";
+                    "ADD CONSTRAINT " +CONSTRAINT_NAME+ " CHECK ( (email IS NOT NULL ) OR (oauth_id IS NULL) ) ;";
             log.debug(sql);
             altTable.executeUpdate(sql);
         }