Reduce concrete execution timeout to 1 second

Author: IlyaMuravjov

utbot-junit-contest/src/main/kotlin/org/utbot/contest/usvm/ContestUsvm.kt

@@ -192,10 +192,7 @@ fun runUsvmGeneration(
                     }
                 }
                 val jcExecutions = states.mapNotNull {
-                    // TODO usvm-sbft: if we have less than `runner.timeout` budget we should only let resolver run
-                    //  for `remainingBudgetMillisWithoutCodegen()` ms, right now last resolver call may exceed budget,
-                    //  essentially stealing some time from codegen
-                    if (remainingBudgetMillisWithoutCodegen() > 0)
+                    if (remainingBudgetMillisWithoutCodegen() > UTestRunner.CONTEST_TEST_EXECUTION_TIMEOUT.inWholeMilliseconds)
                         logger.debug().measureTime({ "resolver.resolve(${method.classId}.${method.signature}, ...)" }) {
                             runCatching {
                                 resolver.resolve(jcTypedMethod, it)

utbot-junit-contest/src/main/kotlin/org/utbot/contest/usvm/executor/UTestRunner.kt

@@ -3,10 +3,11 @@ package org.utbot.contest.usvm.executor
 import org.jacodb.api.JcClasspath
 import org.usvm.instrumentation.executor.UTestConcreteExecutor
 import org.usvm.instrumentation.instrumentation.JcRuntimeTraceInstrumenterFactory
-import org.usvm.instrumentation.util.InstrumentationModuleConstants
+import kotlin.time.Duration.Companion.seconds
 
 // TODO usvm-sbft-refactoring: copied from `usvm/usvm-jvm/test`, extract this class back to USVM project
 object UTestRunner {
+    val CONTEST_TEST_EXECUTION_TIMEOUT = 1.seconds
 
     lateinit var runner: UTestConcreteExecutor
 
@@ -18,7 +19,7 @@ object UTestRunner {
                 JcRuntimeTraceInstrumenterFactory::class,
                 pathToJars,
                 classpath,
-                InstrumentationModuleConstants.testExecutionTimeout
+                CONTEST_TEST_EXECUTION_TIMEOUT
             )
     }
 }