Upgrade liquibase version to avoid a bug where a changeset is executed twice

Closes #23220

(cherry picked from commit 7f2f4aae67)

Conflicts:
	testsuite/integration-arquillian/tests/base/src/test/java/org/keycloak/testsuite/zerodowntime/ZeroDowntimeTest.java

model/jpa/src/main/java/org/keycloak/connections/jpa/updater/liquibase/custom/CustomCreateIndexChange.java

@@ -74,7 +74,7 @@ public class CustomCreateIndexChange extends CreateIndexChange {
         }
         try {
             // To check that the table already exists or not on which the index will be created.
-            if (!SnapshotGeneratorFactory.getInstance()
+            if (getTableName() == null || !SnapshotGeneratorFactory.getInstance()
                 .has(new Table().setName(getTableName()).setSchema(new Schema(getCatalogName(), getSchemaName())), database))
                 return super.generateStatements(database);
 

pom.xml

@@ -138,7 +138,7 @@
         <freemarker.version>2.3.32</freemarker.version>
 
         <jetty9.version>${jetty94.version}</jetty9.version>
-        <liquibase.version>4.20.0</liquibase.version>
+        <liquibase.version>4.23.2</liquibase.version>
         <osgi.version>4.2.0</osgi.version>
         <pax.web.version>7.1.0</pax.web.version>
         <servlet.api.30.version>1.0.2.Final</servlet.api.30.version>