[MINOR] Upgrade Surefire to 3.5.2 and enforce fork exit timeout

Fix intermittent ~26 minute hangs in the **.component.c**.** GitHub
Actions job. The forks were finishing their test classes but failing
to exit cleanly (leaked non-daemon threads from test executors), and
Surefire 3.0.0 did not reliably enforce its fork shutdown timeout.

Author: Baunsgaard

pom.xml

@@ -53,7 +53,7 @@
 		<slf4j.version>2.0.11</slf4j.version>
 		<log4j.version>2.22.1</log4j.version>
 		<maven-clean-plugin.version>3.2.0</maven-clean-plugin.version>
-		<maven-surefire-plugin.version>3.0.0</maven-surefire-plugin.version>
+		<maven-surefire-plugin.version>3.5.2</maven-surefire-plugin.version>
         <maven-checkstyle-plugin.version>3.3.1</maven-checkstyle-plugin.version>
 		<maven-remote-resources-plugin.version>3.0.0</maven-remote-resources-plugin.version>
 		<maven-javadoc-plugin.version>3.5.0</maven-javadoc-plugin.version>
@@ -410,6 +410,10 @@
 					<reuseForks>false</reuseForks>
 					<!-- Kill hung test forks before CI cancels the whole job. -->
 					<forkedProcessTimeoutInSeconds>${test-forkedProcessTimeout}</forkedProcessTimeoutInSeconds>
+					<!-- Force-kill forks that still have live threads after the test class completes. -->
+					<forkedProcessExitTimeoutInSeconds>30</forkedProcessExitTimeoutInSeconds>
+					<!-- Let forks detect a dead parent and self-terminate. -->
+					<enableProcessChecker>native</enableProcessChecker>
 					<!-- <reportFormat>brief</reportFormat> -->
 					<trimStackTrace>true</trimStackTrace>
 					<rerunFailingTestsCount>${rerun.failing.tests.count}</rerunFailingTestsCount>