fix: increase Java test timeout from 15s to 120s

[mashraf-222]

Problem

Java optimization was completely broken due to test timeouts. When running benchmarks on Java code, all optimization candidates were failing with:

ERROR: Maven test execution timed out after 15 seconds

This meant no Java code could be optimized through codeflash.

Root Cause

The 15-second test timeout was designed for Python's pytest, which starts almost instantly. Java's Maven has significant overhead:

• Maven startup: 2-5 seconds
• Test compilation: additional time
• Test execution: actual test time

With only 15 seconds total, Maven couldn't even finish starting up before timing out.

Solution

Added a Java-specific timeout of 120 seconds that gives Maven enough time to:

1. Start up (2-5s)
2. Compile tests
3. Run benchmarks with multiple loops
4. Collect timing data

Code Changes

config_consts.py: Added Java timeout constant

INDIVIDUAL_TESTCASE_TIMEOUT = 15  # For Python pytest
JAVA_TESTCASE_TIMEOUT = 120  # Java Maven tests need more time

test_runner.py: Applied Java timeout when framework is JUnit5

• Checks if test framework is "junit5"
• Uses max(pytest_timeout, JAVA_TESTCASE_TIMEOUT) to respect explicit higher values
• Adds debug logging when timeout is increased

Safety

This change ONLY affects Java tests:

• Python/pytest: Still uses 15s ✓
• JavaScript/Jest: Still uses 15s ✓
• Java/JUnit5: Now uses 120s minimum ✓

If you explicitly pass a higher timeout, it's respected.

Testing

• ✅ All 339 existing tests pass (2 test_runner + 337 Java tests)
• ✅ E2E Java optimization now completes successfully
• ✅ Original code benchmarked at 64.7ms per loop over 5 loops
• ✅ 143 tests passed in E2E run (12 existing + 131 generated)

Before/After

Before:

❌ Maven test execution timed out after 15 seconds
❌ No optimizations found

After:

✅ Original code: 64.7ms per loop (5 loops completed)  
✅ All tests passing
✅ Optimization candidates being evaluated successfully

This unblocks Java optimization entirely.