Voice: Discord new encryption modes not supported (aead_aes256_gcm_rtpsize)

## Problem

When the bot joins a voice channel, the following error appears repeatedly in the logs:

```
[ERROR] [AudioWebSocket]: None of the provided encryption modes are supported: ["aead_aes256_gcm_rtpsize","aead_xchacha20_poly1305_rtpsize"]
```

The bot cannot play audio in voice because Discord now requires these encryption modes for voice connections, and the current JDA version (4.4.1_353) does not support them.

## Environment

- JMusicBot (current master/snapshot build)
- JDA 4.4.1_353
- Discord voice connection

## Possible directions

1. **Upgrade JDA** to a version that supports the new encryption (e.g. JDA 5.x), which would require dependency and possibly code updates (e.g. JDA-Utilities vs JDA-Chewtils for JDA 5).
2. **Document workarounds** for users (e.g. using Lavalink for audio, or linking to a 4.x JDA build if one adds support).
3. **Backport** the voice encryption support into a 4.x-compatible JDA build if such a release becomes available upstream.

Opening this issue so the maintainers can decide how to address voice support with Discord's current requirements.

Start by reviewing the AudioWebSocket error and the current JDA 4.4.1_353 dependency, then compare the upgrade, workaround, and backport directions described in the issue. Check the impact on JDA-Utilities and JDA-Chewtils before choosing an approach. Done means Discord voice connections support the required encryption modes and the bot can play audio again.

Written by the indexing model from the issue text.