Add voice log to track join and leave events

[Rinzii]

Summary

This PR introduces a new voice log command that provides a recent history of voice join and leave activity for a channel. The intent is to give moderators a practical way to identify who entered or exited a voice channel when an incident happens too quickly to observe live.

It also includes dev-only tooling to generate voice join/leave events for testing. That tooling is isolated and can be removed after review if desired.

New

• Added a new voice log command for viewing recent voice join/leave activity in a voice channel.
• Added paginated output, non-pinging user mentions, and message controls for the voice log.
• Added a dev-only /dev-voice-bounce command for generating voice join/leave events during testing.

Changes

• Updated guild lookup output to use paginated embed-based navigation.

The previous guild lookup response was a flat text dump of channels. Honestly this approach does not scale well once the result set becomes large, and it can be quite awkward to navigate after the initial response is sent. Moving the command to a paginated embed makes the output easier to read, keeps it manageable for larger guilds, and provides a more consistent interaction model for commands that return structured lists.

• Improved slash-command handling for unknown or stale command/subcommand interactions.

Previously, the slash-command handler assumed the incoming interaction always matched the bot’s currently loaded command registry. In practice that assumption does not always hold, particularly during deploys, after command changes, or while Discord is still serving older command definitions. The new handling guards those cases explicitly so the bot responds safely instead of raising an avoidable runtime error. This should make command handling more robust and reduce noise from stale interactions.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud