Feature request: optional autoKill for the gdb server

[AntonKrug]

Now when the renode has the autoStart for GDB:

sysbus.cpu StartGdbServer 5000 true

Connecting with GDB into it will automatically start the cpu/emulation. I'm wondering how viable and difficult it would be to have a separate optional argument (with the default value set to false) to autoKill. AutoKill would stop everything and terminate renode on any gdb connection lost (either by fault/error or by human just regularly disconnecting the gdb)