[Build] Set extended timeout for long running jdt.core tests

Set the following extended timeouts
- for org.eclipse.jdt.core.tests.compiler to 90min (usually runs ~45min)
- for org.eclipse.jdt.core.tests.model to 30min (usually runs ~15min)

This extends the general timeout, which could be too strict in this case
and is introduced via
- eclipse-platform/eclipse.platform.releng.aggregator#3427

Author: HannesWell

org.eclipse.jdt.core.tests.compiler/pom.xml

@@ -24,6 +24,7 @@
 
   <properties>
     <defaultSigning-excludeInnerJars>true</defaultSigning-excludeInnerJars>
+    <surefire.timeout>5400</surefire.timeout><!-- timeout in seconds -->
   </properties>
 
   <build>

org.eclipse.jdt.core.tests.model/pom.xml

@@ -25,7 +25,7 @@
   <properties>
     <defaultSigning-excludeInnerJars>true</defaultSigning-excludeInnerJars>
     <jitExclusion>-XX:CompileCommand=exclude,org.eclipse.jdt.internal.core.dom.rewrite.ASTRewriteAnalyzer::getExtendedRange</jitExclusion>
-
+    <surefire.timeout>1800</surefire.timeout><!-- timeout in seconds -->
   </properties>
 
   <build>