Reviewed-by: kh1

Could not be tested with actual QML project yet.

Reviewed-by: kh1

The device configuration widget is now the only place the user
ever has to specify ports.

Use Debugger::DebuggerRunControl directly instead of wrapping it
into another RunControl.

Reviewed-by: hjk

Reviewed-by: kh1

Fixes: - react on build/ run configuration changes
       - now notices environment changes, like switching Qt versions
       - start button is now only shown if we have a valid qemu runtime
       - enabled/ disabled state works properly when loading a project

Task-number: QTCREATOR-210, QTCREATORBUG-1252, QTCREATORBUG-1082
Reviewed-by: ck

Fixes: - react on build/ run configuration changes
       - now notices environment changes, like switching Qt versions
       - start button is now only shown if we have a valid qemu runtime
       - enabled/ disabled state works properly when loading a project

Task-number: QTCREATOR-210, QTCREATORBUG-1252, QTCREATORBUG-1082
Reviewed-by: ck

Reviewed-by: kh1

Reviewed-by: kh1

Task-number: QTCREATOR-207
Reviewed-by: ck

Renamed RunConfiguration::configurationWidget to
createConfigurationWidget.

Reviewed-by: dt

Functionality depends entirely on the active start-up project, all other
projects should have the the button disabled if they have no Maemo run
config or the the run config is not the active on.

Reviewed-by: ck

 * kh1 says there is no such thing as there is no technical
   destinction between Maemo devices and the Maemo emulator.

Reviewed-by: kh1

Since we use addAutoReleasedObject we would rather unclean call the
class destructor.