This way we don't need a human manually setting it up every time.

Depends on D6333

I deployed this to my keyserver in production and tested with patches like this where I:

1. Overrode the cron time to get it to run when I wanted
2. Overrode the current date to test how it would work on specific dates
3. Made it create test threads in a channel nobody else could see

I tested the following scenarios:

1. Script runs on Monday and there is no event in calendar (thread was not created)
2. Script runs on Monday and there is an event in calendar indicating dev sync is on Tuesday (thread was created)
3. Script runs on Tuesday and there is no event in calendar (thread was created)
4. Script runs on Tuesday and there is an event in calendar indicating dev sync is on Tuesday (thread was not created)