Admin commands: kick, pause, force-advance map

Description

Server administrators need tools to manage live races: kick disruptive players, pause a race for technical issues, and force-advance to the next map. These are essential for smooth operation at release.

Acceptance Criteria

• /admin kick <player> [reason] removes a player from the race and returns them to lobby (not a server kick)
• /admin pause freezes all player movement (velocity = 0), pauses the phase timer, displays "Race paused" to all players
• /admin resume restores movement and timer from where they were paused
• /admin next-map ends the current map immediately and advances to the next in the cup (or ends the cup if on the last map)
• All admin commands require the voyager.admin permission
• Commands are registered via the Cloud command framework
• Each command logs its use with admin UUID, timestamp, and arguments to the server log

Technical Details

• New AdminCommandModule in server module
• Pause/resume: new PausedComponent on the game entity that PhysicsSystem and CupSystem respect
• Permission check uses Minestom permission API

Dependencies

• Permission system ticket (below) should be done first or in parallel

Estimate

M

Start in the server module by reading the Cloud command framework integration, the permission-system ticket, PhysicsSystem, and CupSystem. Design the AdminCommandModule around the listed kick, pause, resume, and next-map behaviors, including Minestom permission checks and server logging. Done means every acceptance criterion is met and the commands work across the current and final cup maps.