Optimization for the handling of the "Running order log"

Current Situation

• The completion of running logs is event-based, and log parts are automatically added to the corresponding log window.
• The order log entries OrderStarted, OrderProcessingStarted and OrderProcessed are provided in the separate short-lived threads via the JOC Event API.
• If the running order logs are not opened, all this overhead is unnecessary.

Desired Behavior

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