Removed dulicate saveScreenshots func

[enes-0]

!!!Not finalized!!!

-Removed parallel comparison

📌 References

• Issue: Error: Java heap space Error: Java heap space #304

🎩 What is the goal?

Fix heap memory issues in the Shot library that occur when running screenshot tests with large image differences, causing OutOfMemoryError.

How is it being implemented?

1. ScreenshotsSaver.saveTemporalScreenshots: Previously, saveScreenshots was called twice — once to save to the temporal path and effectively again to save to the report folder. Replaced the second saveScreenshots call with FileUtils.copyDirectory, which copies the already-written files to the report folder instead of recomposing and re-encoding all screenshots into memory a second time.

2. ScreenshotsComparator.compare: Changed screenshots.par.flatMap(...) to screenshots.flatMap(...), removing parallel collection usage. Parallel comparison loads multiple screenshot pairs into memory simultaneously, which multiplies heap usage. Sequential comparison processes one screenshot at a time, trading execution speed for significantly lower peak memory consumption.

How can it be tested?

If it cannot be tested explain why.

• Use case 1: Run screenshot verification tests with a large suite of screenshots that previously caused an OutOfMemoryError — the tests should now complete without heap errors.
• Use case 2: Run screenshot recording and verification end-to-end to confirm temporal screenshots and report folder screenshots are still generated correctly.
  • Record screenshots (executeScreenshotTests -Precord)
  • Verify screenshots (executeScreenshotTests) and confirm the report folder contains the expected images.