Speed up scoring in ForecastAnomalyModel

Custom stride
Is there any reason for having a hard-coded stride (i.e. 1, code here) when running the historical_forecasts in ForecastingAnomalyModel? If the underlying model has a horizon of 10, I might as well set the stride to 10 to have 10x faster scoring processing.