refactor: remove synchronous console logging from GuiPanel initialization

[AmlanDalai]

Overview

This PR cleans up the initialization sequence of the GuiPanel class by removing residual, development-centric System.out.println statements.

Context & Rationale

During the instantiation of GuiPanel, several hardcoded System.out.println calls were being executed to track the initialization of ProjectManager, ClassifierManager, and FeatureManager.

While useful during early development, leaving synchronous standard output calls in production UI code introduces a few issues:

1. Console Clutter: It unnecessarily spams the standard output stream for end-users.
2. Standard Practices: In the context of ImageJ plugin development, if runtime logging is required, the native IJ.log() should be utilized instead of standard Java print streams so the user can access it via the ImageJ Log window.
3. Clean Architecture: Removing these lines improves the overall code hygiene and keeps the constructor focused solely on component initialization.

Changes Included

• Removed 4x System.out.println statements from the GuiPanel(ProjectManager projectManager) constructor.

Impact

Zero impact on core segmentation logic or UI behavior. This is strictly a code-quality and cleanup improvement to ensure a cleaner runtime environment.