docs: Mention --disable-sigusr1 in getting started guide (#7857)

* Mention --disable-sigusr1

Signed-off-by: Daniel <16339876+dreusel@users.noreply.github.com>

* Update apps/site/pages/en/learn/getting-started/debugging.md

Co-authored-by: Aviv Keller <me@aviv.sh>
Signed-off-by: Daniel <16339876+dreusel@users.noreply.github.com>

* fix formatting

---------

Signed-off-by: Daniel <16339876+dreusel@users.noreply.github.com>
Co-authored-by: Aviv Keller <me@aviv.sh>
Co-authored-by: Michael Esteban <mickel13@gmail.com>

Author: 3 people

apps/site/pages/en/learn/getting-started/debugging.md

@@ -129,6 +129,7 @@ The following table lists the impact of various runtime flags on debugging:
 | --inspect-brk=[host:port]          | Enable inspector agent; Bind to address or hostname host (default: 127.0.0.1); Listen on port port (default: 9229); Break before user code starts     |
 | --inspect-wait                     | Enable inspector agent; Listen on default address and port (127.0.0.1:9229); Wait for debugger to be attached.                                        |
 | --inspect-wait=[host:port]         | Enable inspector agent; Bind to address or hostname host (default: 127.0.0.1); Listen on port port (default: 9229); Wait for debugger to be attached. |
+| --disable-sigusr1                  | Disable the ability of starting a debugging session by sending a SIGUSR1 signal to the process.                                                       |
 | node inspect script.js             | Spawn child process to run user's script under --inspect flag; and use main process to run CLI debugger.                                              |
 | node inspect --port=xxxx script.js | Spawn child process to run user's script under --inspect flag; and use main process to run CLI debugger. Listen on port port (default: 9229)          |