Update rbnacl 4.0 -> 5.0

What does this MR do?

Update rbnacl to latest upstream release. No breaking changes as per https://github.com/crypto-rb/rbnacl/blob/master/CHANGES.md

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Debian already has rbnacl 5.0 and keeping dependencies in sync helps in packaging.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Review
  • Has been reviewed by UX
  • Has been reviewed by Frontend
  • Has been reviewed by Backend
  • Has been reviewed by Database
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• Internationalization required/considered
• End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?