Directly enqueue Battle.net messages in CTL

As the relevant PR adding BNSendGameData support is still outstanding on
the merge front, let's for now just directly poke at its innards and
enqueue such messages directly.

This is the lesser of two evils compared to what Chomp used to do, and
means we can actually ship this new version of Chomp _today_ without
comms being nerfed by 40% on retail.

.luacheckrc

@@ -30,6 +30,7 @@ read_globals = {
 
 	-- ChatThrottleLib
 	"ChatThrottleLib.BNSendGameData",
+	"ChatThrottleLib.Enqueue",
 	"ChatThrottleLib.SendAddonMessage",
 	"ChatThrottleLib.SendAddonMessageLogged",
 	"ChatThrottleLib.SendChatMessage",
@@ -41,6 +42,7 @@ read_globals = {
 	"BNET_CLIENT_WOW",
 	"BNFeaturesEnabledAndConnected",
 	"BNGetNumFriends",
+	"BNSendGameData",
 	"C_BattleNet.GetFriendGameAccountInfo",
 	"C_BattleNet.GetFriendNumGameAccounts",
 	"C_BattleNet.GetGameAccountInfoByID",

Public.lua

@@ -157,8 +157,23 @@ function Chomp.BNSendGameData(bnetIDGameAccount, prefix, text, priority, queue,
 		error("Chomp.BNSendGameData: prefix: length cannot exceed 16 bytes", 2)
 	end
 
-	local chatType = "WHISPER";
-	ChatThrottleLib:BNSendGameData(PRIORITY_TO_CTL[priority] or DEFAULT_PRIORITY, prefix, text, chatType, bnetIDGameAccount, queue, callback, callbackArg)
+	-- Revisit this logic later if/when CTL merges in BNSendGameData support;
+	-- until then let's poke into its guts.
+
+	if not ChatThrottleLib.Enqueue then
+		return
+	end
+
+	ChatThrottleLib:Enqueue(PRIORITY_TO_CTL[priority] or DEFAULT_PRIORITY, queue or prefix, {
+		f = BNSendGameData,
+		callbackFn = callback,
+		callbackArg = callbackArg,
+		nSize = length + (ChatThrottleLib.MSG_OVERHEAD or 40),
+		n = 3,
+		bnetIDGameAccount,
+		prefix,
+		text,
+	})
 end
 
 function Chomp.IsSending()