docs(dat): note why the fetch trigger must stay non-cancelable (no leak)

The request function internally allocs a request batch and frees it itself
(FUN_007cdea0 reclaims it after dispatch), and returns only an int cancel
token we discard - so flags=0 is fire-and-forget with nothing to release.
A cancelable flag would hand back a handle that leaks if not released.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: 3vcloud

GWToolboxdll/Modules/GwDatTextureModule.cpp

@@ -21,7 +21,10 @@ namespace {
     // Asks the client to fetch a file id (dat or network). Found via its unique DOWNLOAD_FLAG assert
     // string (survives client updates); safe in-game and enqueue-only - the client pumps its own queue.
     using RequestFiles_pt = void(__cdecl*)(uint32_t count, const uint32_t* file_ids, uint32_t flags);
-    constexpr uint32_t kTriggerFlags = 0; // normal priority, non-cancelable
+    // 0 = normal priority, non-cancelable: the client owns and frees the request batch itself, so it's
+    // fire-and-forget with nothing to release. Do NOT add a cancelable flag (0x1/0x10000) - those
+    // return a handle that must be released or it leaks.
+    constexpr uint32_t kTriggerFlags = 0;
     RequestFiles_pt RequestFiles_Func = nullptr;
 
     void WireGameFileTrigger()