- Remove old rfcomm process handler from TrkGdbAdapter, use
  Bluetooth starter instead
- Synchronous connection, remove waitForTrkConnect()
- Move gdb start into Trk version answer, pass on
  settings id hint
- Prevent exit crash triggered by signal gdbProcessFinished()
- Set DebuggerNotReady correctly on AdapterStartFailed when no
  gdb is started yet

Updated the QML front-end to revision 44f3548fde7cf6a87bd3cc8bb1cc0e63cfc5ca4c of qt/kinetic-declarativeui

Fixes a segfault when hovering over QtCleanUpFunction in
qcoreapplication.h.

Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>

specifically, we need it iff the user gets to see the stopped inferior

seems to have been an artifact from an early version. it was
unreachable (gdb going wild notwithstanding), and would do
Strange Stuff (TM) if it ever were reached.

first, try harder to have an up-to-date sources list.
then, use the mapping whenever applicable and available.

when queuing up commands, don't interrupt if we are already waiting
for interruption. that will be the case when other commands area already
queued.

if there are already commands queued for running after temporary break,
then *all* commands must queued up or their order will change.

*in theory*, there is no way we could at any point know more than gdb
knows and tells us about full path names. let's see what practice shows
for the gdbs we support ...

Prepare trk::Launcher to deal with a shared trkdevice.
Add encapsulation for the rfcomm listener process and helper
classes for prompting the user to connect the Bluetooth
device. Add a command line prompt to the trklauncher test.

and fix typo in debug message :)=

the state check is in higher-level functions already

It took two 'u' to undo a '~'.

autotest for QStack dumper
custom structure
array

Reported-By: Tasuku Suzuki

Automatically register qml.qch if found in shared/help/qtcreator.
This is needed for the special 'creator-qml' package.