fix: prevent duplicate and wrong test-to-function associations in Java

Fixed two critical bugs in Java test discovery that caused incorrect
test-to-function mappings:

## Bug 1: Duplicate Test Associations

**Problem**: The function_map contained duplicate keys (both func.name and
func.qualified_name pointing to the same object). When iterating over the map
in Strategy 1, each function was processed twice, causing duplicate test
associations.

**Example**:
- function_map['fibonacci'] → fibonacci function
- function_map['Calculator.fibonacci'] → fibonacci function (same object!)

When matching testFibonacci, it would match TWICE and get added TWICE.

**Fix**: Added duplicate check in Strategy 1 (line 117):
```python
if func_info.qualified_name not in matched:
    matched.append(func_info.qualified_name)
```

## Bug 2: Wrong Test Associations

**Problem**: Strategy 3 (class naming convention) was too broad. It would
associate ALL methods in a class with EVERY test in that class's test file.

**Example**:
- CalculatorTest has testFibonacci and testSumRange
- Strategy 3 strips "Test" → "Calculator"
- Finds ALL methods in Calculator class (fibonacci, sumRange)
- Associates BOTH with EVERY test

Result:
- testFibonacci incorrectly associated with sumRange
- testSumRange incorrectly associated with fibonacci

**Fix**: Made Strategy 3 a fallback - only runs if no matches found yet:
```python
if not matched and test_method.class_name:
```

## Impact

**Before**:
```
Calculator.fibonacci → 3 tests:
  - testFibonacci
  - testFibonacci  (duplicate!)
  - testSumRange   (wrong!)

Calculator.sumRange → 3 tests:
  - testFibonacci  (wrong!)
  - testSumRange
  - testSumRange   (duplicate!)
```

**After**:
```
Calculator.fibonacci → 1 test:
  - testFibonacci  ✓

Calculator.sumRange → 1 test:
  - testSumRange   ✓
```

## Testing

✅ All 24 test discovery tests pass
✅ Verified with real Java project (java-test-project)
✅ Each test now correctly maps to only its target function

This fix is critical for optimization correctness - wrong test associations
would cause incorrect behavior verification and benchmarking results.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: mohamedashrraf222

codeflash/languages/java/test_discovery.py

@@ -115,7 +115,8 @@ def _match_test_to_functions(
 
     for func_name, func_info in function_map.items():
         if func_info.name.lower() in test_name_lower:
-            matched.append(func_info.qualified_name)
+            if func_info.qualified_name not in matched:
+                matched.append(func_info.qualified_name)
 
     # Strategy 2: Method call analysis
     # Look for direct method calls in the test code
@@ -137,9 +138,10 @@ def _match_test_to_functions(
             if qualified not in matched:
                 matched.append(qualified)
 
-    # Strategy 3: Test class naming convention
+    # Strategy 3: Test class naming convention (fallback only)
     # e.g., CalculatorTest tests Calculator, TestCalculator tests Calculator
-    if test_method.class_name:
+    # Only use this if no matches found yet (too broad otherwise)
+    if not matched and test_method.class_name:
         # Remove "Test/Tests" suffix or "Test" prefix
         source_class_name = test_method.class_name
         if source_class_name.endswith("Tests"):