All Regression Tests use IRegressionDefintion classes

Expected Behavior

All unit tests that are specifically just a regression algorithm asserting statistics should be using IRegressionDefinition's classes so that they are picked up and ran by AlgorithmStatisticsRegressions.

Actual Behavior

A few Python regressions are ran as individual unit tests meaning they can not be updated the same as the others by using "regression-update-statistics" : true in config.

Examples:
RunPythonSliceGetByTypeRegressionAlgorithm
DataConsolidatorPythonWrapperTests.RunRegressionAlgorithm
PythonOptionTests.FilterReturnsUniverseRegression
PythonOptionTests.FilterReturnsListRegression

There may be others, best to check references of AlgorithmRunner.RunLocalBacktest

Potential Solution

Create C# IRegressionDefinition classes that contain the information needed for AlgorithmStatisticsRegressions to run these tests.

Checklist

• I have completely filled out this template
• I have confirmed that this issue exists on the current master branch
• I have confirmed that this is not a duplicate issue by searching issues

• I have provided detailed steps to reproduce the issue

Start by inspecting references of AlgorithmRunner.RunLocalBacktest and compare the listed Python regression tests with existing IRegressionDefinition classes. Review how AlgorithmStatisticsRegressions discovers and runs these definitions. Done means the identified regression-only tests use C# IRegressionDefinition classes and can be updated through the regression-update-statistics configuration.