Update gamedig to 5.3.2 and quiet down offline errors

- Update GameDig from 5.1.4 to 5.3.2
- Server-down errors (timeouts, connection refused, DNS failures, etc.)
  no longer call node.error(). The offline msg still flows out and
  status still shows red, but the debug panel stays clean. Real gamedig
  errors (parse failures, unexpected exceptions) still surface as before
- node.error() now passes msg as the second argument so downstream
  catch nodes can handle gamedig errors
- Removed leftover console.error(error) call from the gamedig catch
  block since node.error already handles logging when appropriate
- Switch the admin /gamedig/types call in the editor from $.getJSON to
  RED.comms.request so it respects Node-RED's auth and httpAdminRoot
  prefix. Adds a .fail() handler so editor load errors get logged

query-game-server.html

@@ -41,14 +41,17 @@
                 $("#node-input-strip_colors").prop('checked', true);
             }
 
-            $.getJSON('/gamedig/types', function(data) {
-                if(data.result !== 'ok' || !data.hasOwnProperty("server_types"))
-                {
+            RED.comms.request({
+                url: 'gamedig/types',
+                type: 'GET'
+            }).done(function(data) {
+                if (data.result !== 'ok' || !data.hasOwnProperty("server_types")) {
                     console.error("server_types failed to load");
                     return;
                 }
-
                 server_types = data.server_types;
+            }).fail(function(err) {
+                console.error("Error retrieving server_types:", err);
             });
 
             $("#node-input-server_type").autoComplete({