Draft: Failing stacks

Adds a test that a clearly not focused stack should continue. Due to current testing, instead it accepts and ignores the trend

A fit would show that the expected sharpest point is still to come, but our check for peak considers point (2, 10) as a peak

This needs fixing

Merge checklist:

• All new/changed functions have up to date typehints and docstrings
• Any UI updates have a before and after screenshot in the MR description
• Unit testing of new functionality has similar or better coverage that similar existing code
• This code has been tested on a microscope
  • With webapp has been recompiled (if changed)
  • With updated settings JSON (if changed)
  • SmartScan and live stitching work

Related issues: