chore: [SECURITY] Bump PyNaCL

[Paillat-dev]

Summary

See https://nvd.nist.gov/vuln/detail/CVE-2025-69277

Information

• 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, typehinting,
  examples, ...).

Checklist

• I have searched the open pull requests for duplicates.
• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes.
• If type: ignore comments were used, a comment is also left explaining why.
• I have updated the changelog to include these changes.
• AI Usage has been disclosed.
  • If AI has been used, I understand fully what the code does

[pycord-app]

Thanks for opening this pull request!
Please make sure you have read the Contributing Guidelines and Code of Conduct.

This pull request can be checked-out with:

git fetch origin pull/3281/head:pr-3281
git checkout pr-3281

This pull request can be installed with:

pip install git+https://github.com/Pycord-Development/pycord@refs/pull/3281/head

[JustaSqu1d]

no

[vmphase]

FYI, you're not even affected by this CVE. The vulnerability itself is in libsodium's crypto_core_ed25519_is_valid_point, but pycord's pynacl usage is through nacl.secret.SecretBox (XSalsa20-Poly1305) for RTP packet encryption, which never touches the Ed25519 codepath where the bug lives.