On Symbian Qt errors are prefixed with '[Qt Message] '

Task-number: QTCREATORBUG-3694

Reviewed-by: hjk

FileInProjectFinder implements an heuristic to find the likely source
file for an aribrary file path, e.g. in the shadow build folder or
on the device. This is useful especially for .qml files, which are
executed at runtime.

Reviewed-by: con

I didn't manage to find one regular expression that matches both lines with and
without column correctly. Instead use two distinct ones ...

Task-number: QTCREATORBUG-3022

Try to map absolute paths pointing to files in shadow build directory
/ on the device to the respective files in the project directory.

Task-number: QTCREATORBUG-2371
Reviewed-by: dt

Krazy was complaining about those.

Reviewed-by: Tobias Hunger

Reviewed-by: Tobias Hunger

By making the QtOutputFormatter smarter. If we have nothing to format as
a link we do the minimal amount of insertText calls now.

Task-Nr: QTCREATORBUG-2367

 * Make information raised by Qt assert clickable.

Task-number: QTCREATORBUG-2175
Reviewed-by: Olivier Goffart

Works on Windows now. Done with and reviewed by dt, so blame him
if it is now broken on Unix.

Done-with: dt

Reviewed-By: Erik Verbruggen

Fixes a regression introduced in 7862e312.

Reviewed-by: dt

Move link handling code to outputwindow from OutputFormatter

Move createOutputFormatter to the RunConfiguration

That makes it easier for Qt4RunConfiguration et all.
This also fixes that each time a runcontrol was rerun a new
OutputFormatter was created without deleting the old one, thus
increasing the memory usage.

Task-number: QTCREATORBUG-1790
Reviewed-by: dt
Reviewed-by: mae

So now the "Applciation Output" can distinguish between these four, and
handle them appropriately.

By introducing the OutputFormatter, RunControls can influence the formatting
depening on the application started. A nice (and intended) side-effect is that
the QML runtime specific formatting will not interfere anymore with anything
else.