doc: update debugger.md

Checklist

• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

doc, debugger

1. Some output seems weird, but that is what we have in the Nod.js 8.1.1.

2. Considering DeprecationWarning in the outputs, is Stability: 2 - Stable still valid?

3. I've duplicated the note about UUID as it is a part of the debug output now.

4. quit command from the old output throws now:

   debug> quit
   repl:1
   quit
   ^
   
   ReferenceError: quit is not defined
       at repl:1:1
       at ContextifyScript.Script.runInContext (vm.js:53:29)
       at Object.runInContext (vm.js:108:6)
       at REPLServer.controlEval [as eval] (node-inspect/lib/internal/inspect_repl.js:521:25)
       at REPLServer.onLine (repl.js:433:10)
       at emitOne (events.js:115:13)
       at REPLServer.emit (events.js:210:7)
       at REPLServer.Interface._onLine (readline.js:278:10)
       at REPLServer.Interface._line (readline.js:625:8)
       at REPLServer.Interface._ttyWrite (readline.js:904:14)
   debug>

   In the output of the help command there is only this suitable command:

   kill                  Kill a running application or disconnect

   but its behavior is weird: first, it duplicates header lines, then does nothing:

   debug> kill
   < Debugger attached.
   < Debugger listening on ws://127.0.0.1:9229/1af5b6a5-eb79-43be-9f15-f7ba31f8147e
   < For help see https://nodejs.org/en/docs/inspector
   
   debug> kill
   debug>

   .exit seems OK, so I've added it instead.

   I am not sure if some of these nits are bugs that should be addressed.

5. test/fixtures/break-in-module/mod.js seems to be changed recently again (copyright added), so the corresponding example is also updated along with other changes in debug behavior.

6. Inspector output is also updated.

7. 'Chrome Debugging Protocol' link is replaced according to the current redirection.