Capture and report server crash after RESTORE in corrupt-dump-fuzzer test (#14836)

## Problem

In `corrupt-dump-fuzzer.tcl`, after a successful `RESTORE` with a
corrupted payload, the test did a bare `r ping` to check whether the
server was still alive:

If the server crashed at this point, the uncaught exception would
**silently terminate the entire test** without printing the payload that
caused the crash, making the issue extremely hard to reproduce and
debug.

## Fix

Wrap `r ping` with catch to ensure failures trigger the same reporting
and restart logic as `RESTORE`. This ensures offending payloads are
logged for reproduction.

tests/integration/corrupt-dump-fuzzer.tcl

@@ -145,7 +145,13 @@ foreach sanitize_dump {no yes} {
                         }
                     }
                 } else {
-                    r ping ;# an attempt to check if the server didn't terminate (this will throw an error that will terminate the tests)
+                    # an attempt to check if the server didn't terminate (this will throw an error that will terminate the tests)
+                    if { [catch { r ping } err] } {
+                        set msg "Server crashed after RESTORE with payload: $printable_dump"
+                        write_log_line 0 $msg
+                        puts $msg
+                        error $err
+                    }
                 }
 
                 set print_commands false