Implement Warden module execution foundation (Phase 1 & 2)

Added architecture for loading and executing native x86 Warden modules:

New classes:
- WardenModule: Individual module loader with 8-step pipeline
  ✅ MD5 verification (working)
  ✅ RC4 decryption (working)
  ⏳ RSA/zlib/exe-parsing/relocation/API-binding/execution (TODOs)
- WardenModuleManager: Module lifecycle and disk caching
  ~/.local/share/wowee/warden_cache/<MD5>.wdn
- WardenFuncList: Callback structure for module execution

Integration:
- Added wardenModuleManager_ to GameHandler
- Module manager initialized on startup
- Foundation ready for phases 3-7 (validation → execution)

Documentation:
- WARDEN_MODULE_ARCHITECTURE.md (comprehensive 7-phase roadmap)
- Estimated 2-3 months for full native code execution
- Alternative: packet capture approach (1-2 weeks)

Status: Crypto layer complete, execution layer TODO

src/game/game_handler.cpp

@@ -1,6 +1,7 @@
 #include "game/game_handler.hpp"
 #include "game/transport_manager.hpp"
 #include "game/warden_crypto.hpp"
+#include "game/warden_module.hpp"
 #include "game/opcodes.hpp"
 #include "network/world_socket.hpp"
 #include "network/packet.hpp"
@@ -72,6 +73,9 @@ GameHandler::GameHandler() {
     // Initialize transport manager
     transportManager_ = std::make_unique<TransportManager>();
 
+    // Initialize Warden module manager
+    wardenModuleManager_ = std::make_unique<WardenModuleManager>();
+
     // Default spells always available
     knownSpells.push_back(6603);  // Attack
     knownSpells.push_back(8690);  // Hearthstone