fix: add Java patterns to instrumented test file cleanup

[mashraf-222]

Problem

Java optimizations were failing when run sequentially because instrumented test files from previous optimizations were not being cleaned up.

Error:

WARNING: Test type not found for 'FibonacciSearchTest__perfonlyinstrumented.java'
WARNING: Couldn't run any tests for original function knapSack. Skipping optimization.
Result: ❌ No optimizations found

This made it impossible to run multiple Java optimizations without manually deleting instrumented files between runs.

Root Cause

The find_leftover_instrumented_test_files() method in optimizer.py has regex patterns to detect and clean up instrumented test files, but it only included patterns for:

• Python: test_.*__perfinstrumented.py
• JavaScript: *__perfinstrumented.test.js

Java patterns were missing:

• *Test__perfinstrumented.java
• *Test__perfonlyinstrumented.java

Solution

Added Java patterns to the cleanup regex:

# Java patterns
r".*Test__perfinstrumented\.java|.*Test__perfonlyinstrumented\.java"

Now the cleanup method (called at line 482 before each optimization) will properly detect and remove Java instrumented test files.

Changes

optimizer.py (line 624-649):

• Added Java patterns to docstring
• Added Java regex patterns to the compiled pattern
• Added pipe | separator before Java patterns

test_cleanup_instrumented_files.py (new file):

• 4 comprehensive test cases covering Java, Python, JavaScript, and mixed scenarios
• Verifies instrumented files ARE detected
• Verifies normal test files are NOT detected
• All tests pass ✓

Testing

✅ Unit tests:

$ pytest tests/test_cleanup_instrumented_files.py -v
test_find_leftover_instrumented_test_files_java PASSED
test_find_leftover_instrumented_test_files_python PASSED  
test_find_leftover_instrumented_test_files_javascript PASSED
test_find_leftover_instrumented_test_files_mixed PASSED
4 passed in 0.05s

✅ Regex validation:

• FibonacciSearchTest__perfonlyinstrumented.java ✓ MATCH
• BruteForceKnapsackTest__perfinstrumented.java ✓ MATCH
• FibonacciSearchTest.java ✗ NO MATCH (correct)

Impact

• ✅ Java optimizations can now run sequentially without manual cleanup
• ✅ Prevents test discovery failures from stale instrumented files
• ✅ Consistent behavior across Python, JavaScript, and Java
• ✅ No breaking changes - only adds missing patterns

This fixes a critical bug blocking Java E2E optimizations.