Allow Codey to make Reminders, Alarms, and Announcements

[derzz]

Summary of Changes

• This will allow Codey to make announcements, timers, and reminders for the user.
• Timers and reminders will be sent as a DM to the user
• Announcements will be sent to the #announcements channel.
• Users can view and delete messages in an ephemeral message.

Related Issues

Issue #541

Steps to Reproduce

• Just run Codey as usual, a reminders and announcements table will be created in the sqlite db.

• /reminder create date time message will create a reminder with an optional date, time, and message. A modal will show to confirm/add any changes.

• /reminder view will show any reminders that are about to be sent.

• /reminder delete will allow the user to delete any reminders that have yet to be sent.

• /timer create minute hours days message will allow the user to create a timer with the time duration included. If multiple time units are included, they will be added. If no message is provided, a default message "Times up!" will be provided.

• /timer view will show any timers that are about to be sent.

• /timer delete will allow the user to delete any timers that have yet to be sent.

• /announcement create date time message photo will allow the user to create an announcement to be displayed in the announcements channel. A modal will pop up allowing the user to verify any changes/add any changes.

• /announcement view will allow the user to pick any sample announcement to view in an ephemeral message.

• /announcement delete will allow the user to delete any announcements that have yet to be sent.

Demonstration of Changes

• What the reminders and timers look like

• Sample announcement view and announcement production

Further Information and Comments

• The server owner must allow the /announcement command to be given to admin roles
• The observer works every minute, so timers and reminders are not perfect to the exact second. This can be adjusted to every second but may be expensive, especially with a bigger db.
• This is a first draft, let me know if anything needs to be added/removed!

[KuroganeToyama]

I haven't reviewed the functionality yet, but I probably should have mentioned this earlier. We do want our code to be conformed and not all messy, so before you make a PR, run yarn lint and fix whatever is being complained about. Otherwise, you're gonna see the failed build showing up on your PR. Once you've done that, I'll review the PR once I have the time (hopefully soon).

[Yohello1]

I should figure out how to uh merge this in, and run it LOL

Edit: Adding myself here so I get notifs, remind me on the weekend to run it ya

[KuroganeToyama]

@Yohello1 , I just made you owner of the repo and owner of the Discord team in GitHub. So ideally, whenever a new PR pops up, you should be pinged for review, and you should be able to merge the PR, as well as pushing directly to main should you need to.

You may have read the wiki already, but I'm just gonna say again just in case. When main is updated, Codey Staging is updated. When a release is made, Codey Prod is updated. And preferably, we would like 1 release every term. That being said, we have never quite stuck to that preference.