Update a bunch of GLib documentation links.

Change our developer.gnome.org/glib URLs to
developer-old.gnome.org/glib. The official documentation for GLib
appears to be at https://docs.gtk.org/glib/, but it has a different
layout than the gnome.org content (and is surprisingly resistant to
exploration IMHO). We can switch to developer-old.gnome.org using a
simple substitution and it still seems to be updated, so do that for
now.

doc/wireshark-filter.adoc

@@ -463,7 +463,7 @@ The latest version of *Wireshark* can be found at
 https://www.wireshark.org.
 
 Regular expressions in the "matches" operator are provided by GRegex in GLib.
-See https://developer.gnome.org/glib/2.32/glib-regex-syntax.html or https://www.pcre.org/ for more information.
+See https://www.pcre.org/ for more information.
 
 This manpage does not describe the capture filter syntax, which is
 different. See the manual page of xref:https://www.tcpdump.org/manpages/pcap-filter.7.html[pcap-filter](7) or, if that doesn't exist,

docbook/wsdg_src/WSDG_chapter_build_intro.adoc

@@ -47,6 +47,6 @@ common data structures.
 ____
 
 GLib contains lots of useful things for platform independent development.
-See https://developer.gnome.org/glib/[] for details about GLib.
+See https://developer.gnome.org/glib/ and https://docs.gtk.org/glib/ for details about GLib.
 
 // End of WSDG Chapter Build Introduction

docbook/wsdg_src/WSDG_chapter_sources.adoc

@@ -298,7 +298,7 @@ Wireshark will immediately alert you to any detected issues.
 $ cmake .. -G Ninja -DENABLE_ASAN=1
 ----
 
-See https://developer.gnome.org/glib/stable/glib-running.html[]
+See https://developer-old.gnome.org/glib/stable/glib-running.html
 
 [[ChSrcWin32Debug]]
 ==== Windows Native

docbook/wsluarm.adoc

@@ -293,7 +293,7 @@ https://rrthomas.github.io/lrexlib/manual.html[]
 
 The GLib Regular expression syntax (which is essentially PCRE syntax) can be
 found at
-https://developer.gnome.org/glib/2.38/glib-regex-syntax.html[]
+https://developer-old.gnome.org/glib/stable/glib-regex-syntax.html[]
 
 [[lua_class_GRegex]]
 

docbook/wsug_src/WSUG_chapter_io.adoc

@@ -482,7 +482,7 @@ way it should be processed e.g. timestamps, encapsulation type etc.
 ==== Regular Text Dumps
 
 Wireshark is also capable of scanning the input using a custom perl regular
-expression as specified by GLib's https://developer.gnome.org/glib/stable/glib-regex-syntax.html[GRegex here].
+expression as specified by GLib's https://developer-old.gnome.org/glib/stable/glib-regex-syntax.html[GRegex here].
 Using a regex capturing a single packet in the given file
 wireshark will search the given file from start to the second to last character
 (the last character has to be `\n` and is ignored)
@@ -609,7 +609,7 @@ Packet format regular expression::
 This is the regex used for searching packets and metadata inside the input file.
 Named capturing subgroups are used to find the individual fields. Anchors `^` and
 `$` are set to match directly before and after newlines `\n` or `\r\n`. See
-https://developer.gnome.org/glib/stable/glib-regex-syntax.html[GRegex] for a full
+https://developer-old.gnome.org/glib/stable/glib-regex-syntax.html[GRegex] for a full
 documentation.
 
 Data encoding::

epan/maxmind_db.c

@@ -48,7 +48,7 @@ static char mmdbr_stop_sentinel[] = "\x04"; // ASCII EOT. Could be anything.
 
 // The GLib documentation says that g_rw_lock_reader_lock can be called
 // recursively:
-//   https://developer.gnome.org/glib/stable/glib-Threads.html#g-rw-lock-reader-lock
+//   https://developer-old.gnome.org/glib/stable/glib-Threads.html#g-rw-lock-reader-lock
 // However, g_rw_lock_reader_lock calls AcquireSRWLockShared
 //   https://gitlab.gnome.org/GNOME/glib/blob/master/glib/gthread-win32.c#L206
 // and SRW locks "cannot be acquired recursively"

wsutil/wmem/wmem_map.h

@@ -40,7 +40,7 @@ typedef struct _wmem_map_t wmem_map_t;
  * the map is fully destroyed. Items stored in it will not be freed unless they
  * were allocated from the same scope. For details on the GHashFunc and
  * GEqualFunc parameters, see the glib documentation at:
- * https://developer.gnome.org/glib/unstable/glib-Hash-Tables.html
+ * https://developer-old.gnome.org/glib/stable/glib-Hash-Tables.html
  *
  * If the keys are coming from untrusted data, do *not* use glib's default hash
  * functions for strings, int64s or doubles. Wmem provides stronger equivalents