Stop Minerva from sending two initializes for the same event

[chrissank]

Sometimes after a /initialize Minerva sends two initialize messages for the same event (denoted by having the same names). Only the first (i.e. the event that occurs the earliest) should be used.

[chrissank]

this happens when there are less than 10 (or something) events that have undefined descriptions over the next week, so it starts to grab the next event in the repeated event as well

[QuantumManiac]

Bug still exists, reproduced in dev:

1. Create a weekly repeating event in the calendar, with it being the only event in the calendar
2. Invoke /initialize in any of the channels in slack
3. you will see an initialization message for the event 10 times: