Suggest enabling performance tracking in the speed analysis findings

[Martin-Molinero]

Description

• The algorithm speed analysis now suggests setting the PerformanceSamplePeriod setting to get the Performance chart with the engine time breakdown. The hint is added to the slow execution (tracked metrics and completion-log fallback) and throughput degradation findings, uses the algorithm's language for the setting name and example, and is skipped when the algorithm already has performance tracking enabled.
• Include the server statistics in the stored intermediate backtest results, matching the split update packets which already carry them.

Related Issue

N/A

Motivation and Context

Helps users diagnose slow backtests by pointing them at the built-in performance tracking tool.

Requires Documentation Change

N/A

How Has This Been Tested?

New unit tests in AlgorithmSpeedAnalysisTests covering the hint's presence, language formatting, and suppression when tracking is already enabled.

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)

🤖 Generated with Claude Code