Bug fix for stats not getting trimmed in the DB for Crowsnest

Looks like the 'timeToExpire' was set only once when Crowsnest started up, but never updated on the 'data' event on line 62. The resulting comparison on line 66 will never evaluate to true, and the data will never be trimmed. This results in CPU spikes and disk issues as the size of the data continues to grow.