As a user, I want to choose whether to keep the Actual Result field when merging a Test Run after modifying a Dataset

Currently, when merging a Test Run that uses a Parameterized Test, the Actual Result field is erased if changes are made to the Dataset (e.g., renaming a parameter). This happens because, after modifying the Dataset, existing Test Runs must be reset, as it is unclear whether the changes affect the meaning of the steps.

However, this behavior differs from how Test Steps are handled, where the Actual Result field is preserved when merging changes.

Actual result/Attachments

The actual Results field is deleted.

Expected result 

Instead of automatically resetting the iteration and clearing the Actual Result field, users should be given the option to choose how to handle the merge. This could be done through a prompt or confirmation dialog when merging a Test Run, allowing them to:

1. Keep the existing Actual Result field (if they are confident the parameter changes do not impact the test).
2. Reset the Actual Result field (if they prefer to ensure consistency).