Wrap all events with Event subclasses

[Bluenix2]

Summary

The way the EventDispatcher works is that all listener callbacks have to be annotated with a subclass of Event. Which means that for each Discord event a subclass has to be created.

Tasks

• CHANNEL_CREATE
• CHANNEL_UPDATE
• CHANNEL_DELETE
• CHANNEL_PINS_UPDATE
• THREAD_CREATE
• THREAD_UPDATE
• THREAD_DELETE
• THREAD_LIST_SYNC
• THREAD_MEMBER_UPDATE
• THREAD_MEMBERS_UPDATE
• GUILD_CREATE
• GUILD_UPDATE
• GUILD_DELETE
• GUILD_BAN_ADD
• GUILD_BAN_REMOVE
• GUILD_EMOJIS_UPDATE
• GUILD_STICKERS_UPDATE
• GUILD_INTEGRATIONS_UPDATE
• GUILD_MEMBER_ADD
• GUILD_MEMBER_REMOVE
• GUILD_MEMBER_UPDATE
• GUILD_MEMBERS_CHUNK*
• GUILD_ROLE_CREATE
• GUILD_ROLE_UPDATE
• GUILD_ROLE_DELETE
• INTEGRATION_CREATE
• INTEGRATION_UPDATE
• INTEGRATION_DELETE
• INTERACTION_CREATE**
• INVITE_CREATE
• INVITE_DELETE
• MESSAGE_CREATE
• MESSAGE_UPDATE
• MESSAGE_DELETE
• MESSAGE_DELETE_BULK
• MESSAGE_REACTION_ADD
• MESSAGE_REACTION_REMOVE
• MESSAGE_REACTION_REMOVE_ALL
• MESSAGE_REACTION_REMOVE_EMOJI
• PRESENCE_UPDATE
• STAGE_INSTANCE_CREATE
• STAGE_INSTANCE_DELETE
• STAGE_INSTANCE_UPDATE
• TYPING_START
• USER_UPDATE
• VOICE_STATE_UPDATE
• VOICE_SERVER_UPDATE
• WEBHOOKS_UPDATE

*This event may- or may not be dispatched.
**It is still unknown how to do this because of the difference between the interaction server and gateway bot.