Optimization for the handling of the "Running task log"

Current Situation

• The completion of running logs is event-based, and log parts are automatically added to the corresponding log window.
• Each job's stdout/stderr chunk is provided in a separate short-lived thread via the JOC Event API.
  • This results in a massive increase in the number of such threads, especially when dealing with many jobs or jobs that produce larger stdout outputs.
• If the running logs are not opened, all this overhead is unnecessary.

Desired Behavior

• Running task log completion should occur via a mechanism that operates only when the corresponding log window (Order History/Task History) is opened.