Restructure BotManager logic to use switch cases.

[tergytrg]

This PR refactors the existing interaction handling logic to use switch statements instead of if-else blocks. This makes the code more concise, easier to read, and it better represents the Interaction categories.

Changes Made:

• Replaced the if-else block with a switch statement that handles each interaction based on its customId.
• Moved the splitting of the customId into a separate variable to make the code more readable.
• Grouped the interactions into categories (onboarding, diplomacy, vote, etc.) for easier management.

Disclaimer:
I have not tested this code as setting up a Discord Application would require a lot of work. I would greatly appreciate if someone with a test-application available could make sure the functionality is unchanged.

[theelicht]

Wat betreft code ben ik het eens dat dit er beter uit ziet, maar ook ik heb nog geen test bot. @Sheepolution kun jij testen of dit werkt?

[Sheepolution]

The idea is good, but I'm not a fan of the nested switch statements.
Instead, we should create an InteractionHandler, with methods like OnDiplomacyButton, OnVoteModal and OnThreadSelectMenu. Even if these methods would consist of a single line.

Don't forget to add breaks for each case, and use idParts instead, since id_parts breaks the eslint rules.

[Sheepolution]

Use idParts instead.

Suggested change

	const id_parts = interaction.customId.split('_');
	const idParts = interaction.customId.split('_');

[Sheepolution]

Don't forget to place a break after each case.

[Sheepolution]

Instead of a nested switch statement, create an InteractionHandler and place the inner switch statement in a method there.

[tergytrg]

An InteractionHandler is a good idea! At that point, is there any reason to distinguish between Button, Modal, and ThreadMenu interactions? I feel like we can leave that to the BotManager, and let the InteractionHandler contain methods like onDiplomacyInteraction and onVoteInteraction to reduce the complexity.