Show logs when clicking on a failed node in GUI

[BaptisteLacroix]

Description
Currently, the GUI (GraphWorkflowVisualizer) allows users to visualize workflow execution and inspect nodes/substeps. However, when a node fails (status = FAIL), the user only sees the node highlighted in red, without any way to directly access the associated logs or error messages.

It would be very helpful for debugging if clicking on a failed node opened a log viewer panel or popup to display the logs/errors related to that node.

Proposed Behavior

• When a node is marked as FAIL and the user clicks on it in the GUI:

  • Display the logs related to that node in a side panel, popup window, or detail frame.
  • If substeps exist, allow drilling down into which substep failed, and show its specific logs.
  • Provide scrolling/copy-to-clipboard functionality for easier debugging.

Acceptance Criteria

• Clicking a red (FAIL) node shows detailed logs in a dedicated UI element.
• Logs are mapped to the correct node/substep.
• Logs remain accessible even after navigating back and forth between views.
• Graceful handling when no logs are available (e.g., show "No logs recorded for this node").

Example UI Ideas

• A collapsible log panel at the bottom of the window.
• A popup dialog with syntax-highlighted logs.
• A tab in the detail_frame when viewing a failed node.

Why this is useful
This would streamline the debugging workflow: instead of checking logs separately in the console or files, users could immediately correlate workflow failures with the corresponding error messages, directly in the GUI.