Codex/feature network migration

[wtbdev]

This pull request introduces significant changes to support a new "core" network runtime alongside the existing legacy implementation. The main focus is on enabling the server to operate in either legacy or core network mode, with a new command context abstraction to allow chat commands to work across both. The changes include new context interfaces, migration of command execution logic, and updates to configuration and server startup to support the new network stack.

Core network support and runtime selection:

• Added configuration (RukkitConfig.NetworkConfig) and runtime checks (isCoreNetworkEnabled) to select between legacy and core network stacks, with new initialization logic in Rukkit.java to create and manage core network components when enabled. [1] [2] [3] [4] [5] [6] [7]

Command context abstraction and migration:

• Introduced ChatCommandContext, ChatCommandContextListener, and RoomCommandContext interfaces, along with the ServerChatCommandContext implementation, to decouple chat command logic from the underlying network stack and enable shared command semantics for both legacy and core modes. [1] [2] [3] [4]
• Updated ChatCommand to support context-based commands with new factory methods and listener management, enabling registration and execution of commands compatible with the new context. [1] [2] [3] [4]

Command execution improvements:

• Enhanced CommandManager with logic to execute chat commands using the new context abstraction for core connections, including permission checks and command echoing, while maintaining compatibility with legacy commands.
• Added a utility method to normalize nested command prefixes for improved command parsing.

Other improvements and refactoring:

• Extended RoomStartGameEvent to support both legacy and core room types, improving event handling compatibility. [1] [2]
• Added a copy constructor to RoundConfig for creating independent room configurations from defaults.