Once the code is stable, change non-local slash command registration to be app-level instead of guild-level

Investigate using i18next or some other solution for localization

Context: https://discordapp.com/channels/952258283882819595/952260763987349594/1103235011190210650

Option name: "Extract Timestamps"

Input message:

We could meet at 01:00 or 02:00

Output message:

Timestamps in message:

<t:0:t> (01:00)
<t:3600:t> (02:00)

It'd be useful to be able to include the autogenerated timestamps inline with a discord chat message. This would require a way to limit the output to only a specific time output (e.g. 8/8/2022 or 4:00 PM).

I'd imagine the syntax being something like:

Here's my discord message where I say I'd like to schedule our meeting for !timestamp-1600.

Would then output something like:

Here's my discord message where I say I'd like to schedule our meeting for [1600].

Where [1600] would be localized to everyone's individual timezone.

The bot receives Etc/GMT-11T-11 instead of Etc/GMT-11, for example

The current message for the ephemeral parameter to the at command states that the parameter defaults to false, but this no longer seems to be the case.

https://github.com/DJDavid98/HammerTimeBot/blob/main/src/locales/en-US/translation.json#L209

For example, running the command /at hour:7 minute:0 timezone:CST6CDT with the bot produces an ephemeral message.

Specifically supplying False or True to the argument results in the correct behavior.

I personally prefer ephemeral to be on by default (the current behavior), but the helptext does not currently match this.

/timestamp at timezone: Etc/GMT-9 results in the bot recognizing Etc/GMT+9

Context: https://discordapp.com/channels/952258283882819595/952260763987349594/1088141463734456500

Reproduce with /timestamp at year: 10000000

/timestamp at year: 1 month: 1 day: 1 hour: 1 minute: 1 second: 1 timezone: CET

results in
Monday, 22 January 0001 01:17

The need to specify a timezone when using the Hammertime bot kind of defeats the purpose of having the bot in a channel. Ideally, the bot would know what timezone a user is in when they call the /timestamp command and the timezone options should default to the user's timezone.

This matches what I imagine is the primary use case of the bot, which is to give your local time so that everyone on the channel sees it in their own local time. The use case of wanting to specify a time in a different timezone from your local timezone is most likely an edge case.

EDIT: This would then also match the behavior of the website, which defaults to the user's system timezone.

Guide: https://gist.github.com/svemat01/80bdd2020916d4b5e52ce4226514d4d5

Allow all commands to be ran from user context