[Feature Request]: Persistence and Display of Local Execution History in Hop GUI

Although Apache Hop already persists execution data, the current experience focuses on static logs, not performance analysis. When optimizing a pipeline, the developer needs to manually check previous executions, note the metrics, and mentally compare them to the current execution. There is no integrated way to visualize the evolution or real gains achieved after an adjustment.

I propose transforming the "Execution Information" tab into a Performance Benchmarking tool within the interface:

Side-by-Side Comparison: The ability to select two executions and immediately see the difference (Δ) in duration and throughput for each transformation.

Trend Visualization: A simple dashboard or graph integrated into the tab, showing the performance trend of the last 10 to 20 executions.

Optimization Feedback: A clear indicator (e.g., Green/Red) showing whether a recent change has actually improved the specific bottleneck being addressed.

The goal is to move beyond simply "storing data" and start "providing insights," allowing developers to validate their optimizations directly within the Hop interface.

Start at Hop GUI's "Execution Information" tab and trace how persisted execution data is currently presented. Define how selecting two executions, showing duration and throughput differences per transformation, displaying trends for the last 10–20 runs, and indicating optimization feedback should work. Done means these benchmarking views are integrated into the tab and support the proposed comparisons and trend visualization.

Written by the indexing model from the issue text.