Backtest analyzer

[jhonabreul]

Description

Implements a backtest analyzer (BacktestAnalyzer) that will summarize important information about the backtest results into human readable messages that will be appended to the results file.

Related Issue

Motivation and Context

Generating human readable results for the backtests.

Requires Documentation Change

How Has This Been Tested?

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>

[jaredbroad]

Please add "abstract string Issue" to base class of analyses;
Translate each to 3-8 word description of why the analysis was triggered.
Review every single "Potential Solution" to ensure they're not actually Issues.
Rename "Potential Solutions" to just "Solutions" for efficiency of tokens.

Add Weight to every Analysis 0-100 - in final result rank by weight; return at most (n, 10?) by weight.
Perform analysis in order of weight of impact.
Stop performing analysis when reach (n) errors detected to save time.