Feature Request Issue 101: Add a support to be able to Capture static and instance initialization blocks in java classes

[rahlk]

Motivation and Context

This change introduces a new entity, InitializationBlock, to accurately model and capture Java static and instance initialization blocks using JavaParser. Previously, these blocks were not explicitly represented, leading to incomplete analysis of class initialization logic.

How Has This Been Tested?

This change has been tested with a newly added test application and a dedicated test case, mustBeAbleToResolveInitializationBlocks, ensuring that initialization blocks are correctly parsed, modeled, and resolved.

Breaking Changes

Yes, this is a breaking change. The introduction of InitializationBlock modifies the existing data model, thereby generating a new filed in the analysis.json requiring updates to any dependent code.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• 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

This change extends JavaParser’s capabilities by introducing an explicit representation for initialization blocks, aligning with existing abstractions such as methods and constructors. The InitializationBlock entity allows for improved static analysis and reasoning about class initialization behavior.