Document privileged debugging

[ktnlvr]

Closing #1269, document a rudimentary root debugging platform runner.

[louwers]

This is way more complicated than just adding sudo to launch.json. Although yes I get it, that is hard to support.

[louwers]

I don't think people using the extension necessarily have lldb-server installed.

[louwers]

Where does the output show up?

You need to set

        "initCommands": [
          "platform select remote-linux", // For example: 'remote-linux', 'remote-macosx', 'remote-android', etc.
          "platform connect connect://localhost:1234",
          "settings set target.inherit-env false", // See note below.
          "settings set target.input-path /dev/tty",
          "settings set target.output-path /dev/tty",
          "settings set target.error-path /dev/tty"
      ],

[louwers]

Suggested change

	Debugging as root on a local machine is possible only with a remote platform. On MacOS/Linux you should be able to prepend the standard platform command with `sudo`/`doas`/`rootdo`. The builtin terminal will prompt you for the credentials.
	Debugging as root on a local machine is possible only with a remote platform. On macOS/Linux you should be able to prepend the standard platform command with `sudo`/`doas`/`rootdo`. The builtin terminal will prompt you for the credentials.

What is the 'standard platform command'?