feat(migrate,ct): update dependency versions and relocate configuration

Moved `flyway.version` and `postgresql.server.version` to the `dataverse-parent` POM for better configuration centralization. Removed their redundant declarations from the root POM to maintain consistency. Enables reusing the values in the new `dataverse-migrate-db` module

Downgraded the PostgreSQL server version from 17 to the one specified in the installation guide (16) to be in sync with the official recommendations.

Author: poikilotherm

modules/dataverse-parent/pom.xml

@@ -150,6 +150,8 @@
         <!-- Major system components and dependencies -->
         <payara.version>6.2025.3</payara.version>
         <postgresql.version>42.7.4</postgresql.version>
+        <postgresql.server.version>16</postgresql.server.version>
+        <flyway.version>10.19.0</flyway.version>
         <solr.version>9.8.0</solr.version>
         <aws.version>1.12.748</aws.version>
         <google.library.version>26.30.0</google.library.version>

pom.xml

@@ -27,7 +27,6 @@
         <packaging.type>war</packaging.type>
 
         <reload4j.version>1.2.18.4</reload4j.version>
-        <flyway.version>10.19.0</flyway.version>
         <jhove.version>1.20.1</jhove.version>
         <poi.version>5.4.0</poi.version>
         <tika.version>2.9.2</tika.version>
@@ -1100,7 +1099,6 @@
                 <skipIntegrationTests>true</skipIntegrationTests>
                 <!-- Once we truly run tests with Testcontainers, this should be switch to "docker", activating ITs -->
                 <packaging.type>docker-build</packaging.type>
-                <postgresql.server.version>17</postgresql.server.version>
 
                 <app.image>gdcc/dataverse:${app.image.tag}</app.image>
                 <app.image.tag>unstable</app.image.tag>