Send CLI commands using `-interpreter-exec` ...rather than sendinmg them bare. The problem is with C-escaping, apparently some commands need C-style escaping while others do not. This should fix the problem for good, will see.

Fix `GDBStXSimpleProcess` to load user's `.gdbinit` We must not pass `-nx` option that inhibit this. Moreover, GDB looks to `HOME` environment which on stock Windows may not be defined. To avoid surprises when used on Windows, define `HOME` environment - if not already - as path to user profile before actually launching GDB.

Remoce `GDBMI_complete >> asString` ...and use generic implementation. `-complete` is implemented as regular MI command (as opposed to reusing implementation of CLI `complete` so this is no longer needed.

Add property API to `GDBDebugger` This allows clients to associate custom data with debugger instance.

Autodetect GDB data directory As a courtesy to the us who use GDB from build tree, try to detect and automatically add --data-directory if no arguments are specified in GDB command (`GDBProcess gdbCommand`).

Add `GDBMIDebugger` tool to test raw MI / CLI. Useful prerry much only for `jv:libgdbs` developers.

Add (utility) `GDBProcess >> gdbCommandParseAndValidate:` to parse and validate given GDB command. This is used both by `GDBLocalProcess` and settings UI.

Fix quoting bug in `#test_directories`

doc: add `libsource-highlight-dev` to build prereqs ...as recent GDB uses it to highlight code when used in terminal.

Set `mi-always-notify` to 'on' (if supported) ...in order to get all notifications. stx:libgdbs and VDB rely on notifications being sent in order to keep internal data and UI up-to-date. If `mi-always-notify` is not supported, things may not work as espected. You have been warned!