ProjectExplorer: Streamline OutputFormatter creation a bit

Note that the concept of a single monolithic OutputFormatter per
RunConfiguration (and why RunConfiguration, not RunControl to start
with?) is unchanged and suboptimal as one cannot easily combine
existing use cases, e.g. Python_and_Qt.

Change-Id: Ibeb8191020387324f22ed313230293597f96e36a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>

src/plugins/qmlprojectmanager/qmlprojectrunconfiguration.cpp

@@ -56,6 +56,7 @@ QmlProjectRunConfiguration::QmlProjectRunConfiguration(Target *target)
     : RunConfiguration(target, Constants::QML_SCENE_RC_ID)
 {
     addExtraAspect(new QmlProjectEnvironmentAspect(this));
+    setOutputFormatter<QtSupport::QtOutputFormatter>();
 
     // reset default settings in constructor
     connect(EditorManager::instance(), &EditorManager::currentEditorChanged,
@@ -147,11 +148,6 @@ QWidget *QmlProjectRunConfiguration::createConfigurationWidget()
     return wrapWidget(new Internal::QmlProjectRunConfigurationWidget(this));
 }
 
-Utils::OutputFormatter *QmlProjectRunConfiguration::createOutputFormatter() const
-{
-    return new QtSupport::QtOutputFormatter(target()->project());
-}
-
 QmlProjectRunConfiguration::MainScriptSource QmlProjectRunConfiguration::mainScriptSource() const
 {
     QmlProject *project = static_cast<QmlProject *>(target()->project());