More thorough debug workaround

Change the debug global variable from BAGSHUI_DEBUG to BAGSHUI_DEBUG_ON
so anyone who got the old !BagshuiDebug addon accidentally installed
by the Turtle WoW launcher installed will stop getting messages.

Author: veechs

Bagshui.lua

@@ -703,10 +703,10 @@ local bagshuiEnvironment = {
 	---@type string
 	BS_LOG_DATE_STRING = "%Y-%m-%d %H:%M:%S",
 
-	-- Ensure debug is never turned on in production by requiring another addon to set BAGSHUI_DEBUG to true prior to Bagshui loading.
-	-- (I'm doing this via a one-line addon named !BagshuiDebug whose only code is BAGSHUI_DEBUG = true).
+	-- Ensure debug is never turned on in production by requiring another addon to set BAGSHUI_DEBUG_ON to true prior to Bagshui loading.
+	-- The !BagshuiDebug addon (in the Debug folder) is an easy way to enable this.
 	---@type boolean
-	BS_DEBUG = _G.BAGSHUI_DEBUG or false,
+	BS_DEBUG = _G.BAGSHUI_DEBUG_ON or false,
 
 	-- Is SuperWoW loaded? Since it's a DLL injection, not an addon, IsAddOnLoaded() won't help here.
 	---@type boolean

Debug/!BagshuiDebug/BagshuiDebug.lua

@@ -1 +1 @@
-BAGSHUI_DEBUG = true
+BAGSHUI_DEBUG_ON = true

Debug/!BagshuiDebug/Readme.md

@@ -5,6 +5,6 @@ Install this addon to enable [Bagshui](https://github.com/veechs/Bagshui)’s de
 
 There are also a few other debug flags scattered around that won’t function otherwise.
 
-All it does is set the global `BAGSHUI_DEBUG` to `true`.
+All it does is set the global `BAGSHUI_DEBUG_ON` to `true`.
 
 This exists as a separate addon so there’s no need to turn off debug for releases, since it’s off by default.