Now the code for each interaction for a command is defined in the original command file
instead of one big file that implements the logic for all commands.

The challenges-talk channel is the only channel that does not have a Discord bot message in it,
so we should include everything in the channel.

These command implementations are a specific implementation of handling interaction,
so it should not be in the global folder.

When we want to introduce new ways of interacting with Discord, we need to separate the current 'agile' implementation with everything else.
This folder structure makes much more sense therefore.

In the future we want to be able to change the handle style of the Discord bot (see #239).
Now we have an easy way of adding new handle styles which can be toggled by .env configuration.

Only the discordHooks.ts needs to be split and reorganized for this to fully work.

The channels.ts file is created with the agile workflow in mind.
Therefore it belongs to the agile subdirectory and it is not a general utility file.

Just like the commands and interactions, the hooks are now also dynamically imported.

This reduces the cognitive complexity a lot and allows for more reusable setup.

It makes more sense to have this function here than in the hooks.ts
since it is related to solving a task and not for hooking.