Reset the MidPrice rolling extremes

[mkzung]

Description

MidPrice never overrode Reset(), so its Maximum and Minimum carried the previous run.

Related Issue

Closes #9693

Motivation and Context

The first bars after a reset were computed from data outside the window. Same class as #9686, #9687 and #9688.

Requires Documentation Change

No.

How Has This Been Tested?

Added ProducesTheSameValuesAfterReset to MidPriceTests, in the shape used in ConnorsRelativeStrengthIndexTests and SuperTrendTests. It fails on master and passes with the override.

Also ran the indicator against Tests/TestData/spy_midprice.txt on a master build and on this one: 496 expected MIDPRICE_5 values, no mismatches either way, so nothing outside the reset path moves.

My local NUnit host crashes on a Python.NET finalizer during test discovery, unrelated to this change, so both runs above were done from a console program linked against each build rather than through dotnet test.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

[Martin-Molinero]

Thanks @mkzung!