Optimize Maven test execution using forked JVMs

Build time went from the 40-50 s range down to the 10-20 s range.

.github/workflows/maven.yml

@@ -33,7 +33,7 @@ jobs:
         restore-keys: |
           ares-maven-
     - name: Test with Maven and JDK ${{ matrix.java }}
-      run: mvn -B clean test
+      run: mvn -B clean test -P fast
   test-gradle:
     runs-on: ubuntu-latest
     strategy:

pom.xml

@@ -316,6 +316,27 @@
 				</snapshotRepository>
 			</distributionManagement>
 		</profile>
+		<!-- Profile for fast builds and tests (~ 16 s) -->
+		<profile>
+			<id>fast</id>
+			<build>
+				<plugins>
+					<plugin>
+						<groupId>org.apache.maven.plugins</groupId>
+						<artifactId>maven-surefire-plugin</artifactId>
+						<version>3.0.0-M5</version>
+						<configuration>
+							<forkCount>4</forkCount>
+							<reuseForks>true</reuseForks>
+							<properties>
+								<!-- There seem to be race conditions with forks and jqwik -->
+								<configurationParameters>jqwik.database=</configurationParameters>
+							</properties>
+						</configuration>
+					</plugin>
+				</plugins>
+			</build>
+		</profile>
 		<!-- Profile for manually deploying to Maven Central -->
 		<profile>
 			<id>ossrh</id>