fix: reject invalid flag in RegisterQueryFile

[Nord1cWarr1or]

🖤

Purpose

RegisterQueryFile() documents that type "can be only RES_TYPE_EXISTS, RES_TYPE_MISSING or RES_TYPE_HASH_ANY", but RES_TYPE_NONE / RES_TYPE_IGNORE were only logged, not rejected: after AMXX_LogError the break leaves the switch and registration continues, returning a handle that only looks alive. Its forward can never fire — ReChecker invokes the query callback only when query->flag == typeFind, and NONE/IGNORE match no resource-check event. Resolves #393.

Approach

One line. After the error log, return FALSE — consistent with the native's other error paths (empty file argument, public callback not found), which already do:

 	case RES_TYPE_NONE:
 	case RES_TYPE_IGNORE:
 		AMXX_LogError(amx, AMX_ERR_NATIVE, "%s: invalid flag type \"%i\".", __FUNCTION__, flag);
-		break;
+		return FALSE;

Open Questions and Pre-Merge TODOs

• Module builds cleanly on Linux 32-bit — only the pre-existing harmless DT_TEXTREL ld warning.
• An invalid flag now returns 0 instead of a dead handle; valid flags (RES_TYPE_EXISTS, RES_TYPE_MISSING, RES_TYPE_HASH_ANY) take the same paths as before.
• Re-checked statically against the ReChecker 2.7 sources (resource.cpp): the callback fires only on query->flag == typeFind.

Learning

Callback invocation condition traced in ReChecker 2.7 resource.cpp.

Resolves: #393

[TheKrytyk]

@s1lentq Can you add this request to master as well as those others? It’s taking an awfully long time