Handle SMSG_CHARACTER_LOGIN_FAILED (0x041) for AzerothCore/Playerbot compatibility

Previously this opcode was unrecognised and silently dropped, leaving the
client stuck in ENTERING_WORLD with no feedback when the server rejected a
login (duplicate session, world down, disabled race/class, etc.). Now we
decode the LoginFailureReason byte, reset state to CHAR_LIST_RECEIVED so
the player can retry, and surface a red error message on the character screen
via the new CharLoginFailCallback. Also adds isError colour support to
CharacterScreen::setStatus so failures show in red and successes in green.

Data/expansions/classic/opcodes.json

@@ -25,6 +25,7 @@
   "SMSG_CHAR_CREATE": "0x03A",
   "SMSG_CHAR_ENUM": "0x03B",
   "SMSG_CHAR_DELETE": "0x03C",
+  "SMSG_CHARACTER_LOGIN_FAILED": "0x041",
   "SMSG_PONG": "0x1DD",
   "SMSG_LOGIN_VERIFY_WORLD": "0x236",
   "SMSG_LOGIN_SETTIMESPEED": "0x042",

Data/expansions/tbc/opcodes.json

@@ -25,6 +25,7 @@
   "SMSG_CHAR_CREATE": "0x03A",
   "SMSG_CHAR_ENUM": "0x03B",
   "SMSG_CHAR_DELETE": "0x03C",
+  "SMSG_CHARACTER_LOGIN_FAILED": "0x041",
   "SMSG_PONG": "0x1DD",
   "SMSG_LOGIN_VERIFY_WORLD": "0x236",
   "SMSG_LOGIN_SETTIMESPEED": "0x042",

Data/expansions/turtle/opcodes.json

@@ -25,6 +25,7 @@
   "SMSG_CHAR_CREATE": "0x03A",
   "SMSG_CHAR_ENUM": "0x03B",
   "SMSG_CHAR_DELETE": "0x03C",
+  "SMSG_CHARACTER_LOGIN_FAILED": "0x041",
   "SMSG_PONG": "0x1DD",
   "SMSG_LOGIN_VERIFY_WORLD": "0x236",
   "SMSG_LOGIN_SETTIMESPEED": "0x042",

Data/expansions/wotlk/opcodes.json

@@ -25,6 +25,7 @@
   "SMSG_CHAR_CREATE": "0x03A",
   "SMSG_CHAR_ENUM": "0x03B",
   "SMSG_CHAR_DELETE": "0x03C",
+  "SMSG_CHARACTER_LOGIN_FAILED": "0x041",
   "SMSG_PONG": "0x1DD",
   "SMSG_LOGIN_VERIFY_WORLD": "0x236",
   "SMSG_LOGIN_SETTIMESPEED": "0x042",