feat: add import-based test discovery for Java

[misrasaurabh1]

Summary

• Add Strategy 4 to Java test discovery: import-based matching
• When a test file imports a class containing the target function, consider it a potential test for that function
• This fixes an issue where tests like TestQueryBlob (which imports and uses Buffer) were not being discovered as tests for Buffer methods

Problem

When running codeflash on aerospike-client-java, test discovery failed to map tests to functions when:

• The test class name doesn't follow naming conventions (e.g., TestQueryBlob instead of BufferTest)
• But the test imports and uses the target class (Buffer)

The previous strategies only matched tests based on:

1. Test method name containing function name
2. Direct method calls to the target function
3. Test class naming convention (CalculatorTest → Calculator)

Solution

Add Strategy 4: Import-based matching

• Extract import declarations from test files
• If a test imports a class containing the target function, consider it a potential test
• This catches cases where test names are unrelated to the class name but still exercise the code

Test plan

• Added test case test_discover_by_import_when_class_name_doesnt_match that reproduces the aerospike-client-java scenario
• Added test case test_discover_by_direct_method_call for direct calls
• All existing test discovery tests still pass

🤖 Generated with Claude Code