fix: ZigZag when no thresholds met

[DaveSkender]

Description

Exploratory investigation to see if the last line is behaving correctly given a new aberrant dataset.
Fixes #616

Checklist

• My code follows the existing style, code structure, and naming taxonomy
• I have performed a self-review of my own code and included any verifying manual calculations
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings and running code analysis does not produce any issues
• I have added or updated unit tests that prove my fix is effective or that my feature works, and achieves sufficient code coverage
• I have added or run the performance tests that depict optimal execution times
• New and existing unit tests pass locally and in the build (below) with my changes

[DaveSkender]

Using the data provided in the linked issue, there is never a full 5% reversal; therefore, no long should have drawn at all!
I'm fixing that here. What was happening is that it got to the end of the history range and simply plotted the incomplete interim results, which is why you see some odd danglers at the end.

[DaveSkender]

The analysis is basically doing this: 1) find the first extreme point that exceeds the 5% threshold (found at low point 222), then 2) try to find the 5% reversal (it never does).

Given this data, it never increases by 5% and that first low point is unconfirmed; therefore, no line should show.

[github-actions]

This Pull Request has been automatically locked since there has not been any recent activity after it was closed. Please open a new Issue for related bugs.