Create timeout command

[Victoria-DR]

What issue is this solving?

Closes #235

Description

• Added timeout command (both non-slash and slash versions).
• The command times out a user using Discord's new timeout functionality, DMs the user, records the event in audit-logs, and records the event in both the infractions and mod_log tables.
• Mods and above cannot be timed out. Timed out users are automatically un-timed out after the specified time has elapsed (we don't need to code this on our end).
• May still need to discuss the following, which was on the linked issue:

  We need to discuss how this may impact how users contact server staff. As we are currently considering moving to a channel-based ModMail-like tool, that would render users in timeout unable to contact staff.

Any helpful knowledge/context for the reviewer?

• Is a re-seeding of the database necessary? No
• Any new dependencies to install? Yes
• Any special requirements to test? The usual, test with different roles to see effects. Minimum role required is Moderator.
  • (e.g., admin perms, alt account, etc.)

Please make sure you've attempted to meet the following coding standards

• [x] Code has been tested and does not produce errors
• [x] Code is readable and formatted
• [x] There isn't any unnecessary commented-out code

[mikejoh12]

I did some quick testing on the input validation for the duration. Some invalid inputs currently get through the RegEx validation and throw errors. One example is using this string for duration: 112sm. This makes the command fail with a couple of error messages. I think the most solid solution is to create a drop-down of duration options which is fairly easy to do with slash commands. This is what the built in Discord timeout command uses. Another option may be to use a combination of an input field for an Integer with a dropdown for units such as minutes, hours, days, weeks.

[mikejoh12]

It would be good to modify the code so that multiple interaction.reply methods are not executed since this causes an Unhandled Promise Rejection, at least when the 2nd reply is in the catch block. One case where this currently happens is if writing to the DB fails. Since we are handling the error already - sending a reply and logging it with console.error it should not have to trigger an additional Unhandled Promise Rejection. I posted some more info on Discord about the issue.