Support for Soundboard and VC effects

[Puncher1]

Summary

This PR adds following:

• Support for the VOICE_CHANNEL_EFFECT_SEND event
• Support for soundboard sounds
  • create_, edit_, delete_
  • Fetch default soundboard sounds
  • Request guild soundboard sounds over the gateway
  • soundboard_sounds property and get_ method (Guild and Client)
  • GUILD_SOUNDBOARD_CREATE, GUILD_SOUNDBOARD_UPDATE, GUILD_SOUNDBOARD_DELETE events
• Related Audit Log events

Current Problems

Current "problems" on Discord's side, which is stated in the related soundboard PR

• There is no GET route for individual sounds or a guild's list of sounds. Guild sound lists can currently only be retrieved via the Gateway. GET routes should be added *
• PATCHing a sound currently clears the sound's volume and emoji if those aren't included in the request. The PR documents this current behavior, let me know once it is fixed **
• Looks like id and sound_id are always the same, but id is optional ***

* As I tested myself, you can also get the soundboard sounds in the GUILD_CREATE event (e.g. on startup).
** Not handled or documented as for now
*** sound_id is always used, id is not implemented

Others

Things which aren't documented in the related Discord PR:

• override_path is not included in any payload anymore -> both default and guild sounds uses an ID now, so e.g. the "bad umm tss" sound's ID is 7 and so the cdn url is https://cdn.discordapp.com/soundboard-sounds/7

Related PRs: discord/discord-api-docs#6025 (voice channel effects), discord/discord-api-docs#6260 (soundboard)

Checklist

Testing pending

• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes.
• This PR fixes an issue.
• This PR adds something new (e.g. new method or parameters).
• This PR is a breaking change (e.g. methods or parameters removed/renamed)
• This PR is not a code change (e.g. documentation, README, ...)

[SvenLie]

When can we expect this to be undrafted and merged? @Puncher1

[Puncher1]

@SvenLie The GET method is still not supported which, at least for me, doesn't make sense to merge it yet.

[Puncher1]

Update

• For the current status, please refer to the PR description
• The 3.x checks are failing. Looks like there's an error in the installation, @Rapptz
• Testing is pending, after that this PR is ready for review

[Rapptz]

3.x is failing due to aiohttp not building on 3.12 and 3.x is latest Python, so CI is blocked on dependencies and not much I can do there.

[Puncher1]

This has been tested and is ready for review now.

[PaulMarisOUMary]

I believe the issues with 3.x have been resolved now. 🎉

[Rapptz]

I've only done a cursory pass at this. It has merge conflicts currently as well, though this feature is pretty complicated and definitely needs documentation on Discord's end for me to merge it.

There are a few things I'm kind of iffy about, some more important than others:

1. The name SoundboardSound is pretty silly, I'm unsure if going Soudboard is any better but it doesn't read as oddly.
2. The machinery to handle opcode 31 in the gateway seems very complicated for what it is. The chunking mechanism is the way it is because it's expected that multiple events flow in and it needs to be synced and waited. I have no reason to believe soundboard sounds operate the same way but I also have no idea if they do. I tried asking to get clarification on this though I haven't gotten a response yet. I'll update you when I do.

[Puncher1]

Alright I'm done with the changes. Because of the name, how about just Sound? And should it be also applied for properties and attributes (e.g. Client.soundboard_sounds -> Client.sounds)?