Use "set logging enabled on/off" instead of deprecated "set logging on/off"

With GNU gdb (Debian 13.2-1) 13.2, I noticed this trace on console when using --backtrace

Warning: 'set logging on', an alias for the command 'set logging enabled', is deprecated.
Use 'set logging enabled on'.

Change-Id: Ic03911ea94aff57dee8f594744147302ef01a1ed
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160143
Tested-by: Jenkins
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>

bin/refcount_leak.py

@@ -32,7 +32,7 @@
 ## II. run test/soffice in gdb and set breakpoints in acquire/release
 ##     with a command to print the backtrace
 
-# set logging on
+# set logging enabled on
 # break foo.cxx:123
 # break foo.cxx:234
 

desktop/scripts/gdbtrace

@@ -3,11 +3,11 @@ echo log will be saved as gdbtrace.log, this will take some time, patience...\n
 handle SIGPIPE SIGXCPU SIG33 SIG35 SIGPWR nostop noprint
 set logging redirect on
 set logging file gdbtrace.log
-set logging on
+set logging enabled on
 set logging overwrite on
 run
 bt
 thread apply all bt
 quit
-set logging off
+set logging enabled off
 echo log is saved as gdbtrace.log\n

solenv/bin/gdbtrycatchtrace

@@ -12,10 +12,10 @@ end
 echo log will be saved as gdbtrace.log, this will take some time, patience...\n
 set logging redirect on
 set logging file gdbtrace.log
-set logging on
+set logging enabled on
 set logging overwrite on
 run
 bt
 quit
-set logging off
+set logging enabled off
 echo log is saved as gdbtrace.log\n