Add AoC task functionality

[Robin5605]

Closes #44

This is meant to be a proof of concept, and get the basic functionality working. There are a few things that could be improved upon (better error messages, use embeds instead of regular messages for info messages, better info messages, etc), and some features such as restricting the command to certain users/roles (admins/owners) have been left out for the time being, as I do not have enough information to code that up. However, that should be relatively easy. I welcome any and all suggestions to improve upon this, especially in the "design" department with error messages and embeds for info messages.

[Robin5605]

Should now reflect this comment

[camcaswell]

The test is failing intentionally at the moment because there's a placeholder for a thread that doesn't exist yet. You can test locally by simply defining it in your .env, and I'll commit the thread ID when we create it.

Contributed to the PR

[minalike]

I have a couple suggested changes but no blockers.

Tested the following things:

• Starting and stopping event
• Permission role lock
• Force-posting a question
• Setting a custom scheduled post-time other than UTC midnight (it posted!)

screenshots

Forced post

Scheduled post at 3AM UTC (11PM my time)

logs if you are interested

sir-robin              | 2022-08-02 02:46:52,538 | async_rediscache.types.base | DEBUG | Released <NamespaceLock namespace='sir-robin.SummerAoC.cache' [unlocked]> for RedisCache.update
sir-robin              | 2022-08-02 02:46:52,701 | bot.exts.summer_aoc | INFO | Starting Summer AoC event with self.year=2017 self.current_day=7 self.day_interval=1
sir-robin              | 2022-08-02 02:46:52,704 | bot.exts.summer_aoc | DEBUG | Waiting until 3:00 UTC to start Summer AoC loop
sir-robin              | 2022-08-02 03:00:00,790 | bot.exts.summer_aoc | INFO | Posting puzzle for day 7
sir-robin              | 2022-08-02 03:00:01,809 | async_rediscache.types.base | DEBUG | Trying to acquire <NamespaceLock namespace='sir-robin.SummerAoC.cache' [unlocked]> for RedisCache.update
sir-robin              | 2022-08-02 03:00:01,811 | async_rediscache.types.base | DEBUG | Acquired <NamespaceLock namespace='sir-robin.SummerAoC.cache' [locked]> for RedisCache.update
sir-robin              | 2022-08-02 03:00:01,814 | async_rediscache.types.cache | DEBUG | Updating the cache with the following items:
sir-robin              | {'is_running': True, 'year': 2017, 'current_day': 8, 'day_interval': 1, 'post_time': 3}
sir-robin              | 2022-08-02 03:00:01,824 | async_rediscache.types.base | DEBUG | Released <NamespaceLock namespace='sir-robin.SummerAoC.cache' [unlocked]> for RedisCache.update

If there are suggestions for other things I should test, let me know. I plan on testing how it fares with a bot restart.

[janine9vn]

Two big things:

1. Required change in pyproject.toml so this doesn't break locally and we can test it. We'll have to take a look into our redis cache code to adopt to the the async_rediscache breaking changes when it was migrated to aioredis v2.

2. There's a bug I can't quite hunt down but it might be in utils/next_time_occurrence(), but if I start RoC there's an issue with the timestamp generation for when the next puzzle will be posted. It'll say the next puzzle will be posted at the exact time that message was posted. This doesn't happen when I force a post, but as far as I can tell it does when it's regularly scheduled.

I don't think it's an issue with naive timestamps and running in non-utc since arrow does non-naive by default. I'm going to let my bot run for the next 24 hours to see if it's an issue with any scheduled post or just for the first one.

The rest of the comments are more run-of-the-mill or musings that can be ignored or deferred. As a general note, it might be worth prefixing a lot of the internal functions with _ just to maintain code style cohesion with the rest of our code base (thinking Lance and Bot). But that's also very minor and very much up for debate.

[janine9vn]

All my blocker comments are resolved and it works nicely~