Feature Request Issue 125: Analyze test classes optionally if the user wants to

[rahlk]

Motivation and Context

Currently, the tool ignores test classes when analyzing Java projects built with Maven and Gradle. This omission leads to incomplete analysis, as test classes often contain important dependencies, call sites, and code interactions that should be considered.

This PR adds support for detecting and processing test classes from:

• Maven projects (src/test/java/, compiled to target/test-classes/)
• Gradle projects (src/test/java/, compiled to build/classes/java/test/)

How Has This Been Tested?

• Manually verified that test classes are correctly recognized in Maven and Gradle projects.
• Checked that test class handling does not interfere with main class analysis.
• Since this is an enhancement to the processing pipeline rather than a functional feature, no new test cases are required.

Breaking Changes

• No breaking changes; this is an additive feature to existing ones in PR Feature Request Issue 102: Enrich comment analysis capabilities #124
• Existing functionality remains unchanged, but additional test-related data is now included in the analysis.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality to PR Feature Request Issue 102: Enrich comment analysis capabilities #124)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the Codellm-Devkit Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional Context

• Codeanalyzer now adds a new flag --include-test-classes which forces the application to be built by compiling test classes. To enable this feature, you are to use that flag.