add lookback_count to StatusCheck

Graphite data intervals may vary and the 'lookback_count', or the number of recent Graphite data points to consider when doing checks should not be coupled to the 'frequency' of running of checks. I've introduced a 'lookback_count' attribute to the StatusCheck model, which defaults to the 'frequency' of checks to allow for easy migration and backwards compatibility.