SYSREG2 is unable to reliably emit the "bt" command at the kdb:> prompt

When GCC-compiled ReactOS crashes during testing (on our testbots) and enters the KDBG kernel debugger, the kdb:> prompt is emitted.
Our automated testing framework SYSREG2 is in principle able to catch this condition and automatically emit a bt command to request the debugger to display a full backtrace at the point of the crash.

However, it seems this functionality somewhat regressed.
For example, in https://build.reactos.org/#/builders/12/builds/4735/steps/1/logs/stdio , we can observe a SYSREG timeout without the trace being displayed:

Entered debugger on first-chance exception (Exception Code: 0xc0000420) (Assertion Failure)

kdb:>

[SYSREG] timeout

[SYSREG] Stage took: 200.038086 seconds

To remedy this, for the time being, commit 52192f19d6 always trigger a backtrace display whenever the interactive kernel debugger loop is entered. This is not a proper fix, which should be done in SYSREG2 code
(see https://git.reactos.org/?p=sysreg2.git;a=blob;f=console.c;hb=254dbb61fad194f76cadbf43589c35bddb68f425#l173).
(Side-note, our older SYSREG3 (sic.) does something similar as well: https://git.reactos.org/?p=sysreg3.git;a=blob;f=LogReader.cs;hb=e8a1478b1c72817ef32e70a7c65e057dc1e40662#l30 .)

The temporary hackfix has also the "benefit", for ReactOS beginner users, to automatically display the backtrace even if they don't know (or forgot) to take one, when being asked to provide a ReactOS debug log.