Valgrind: Remove CallgrindController's use of ValgrindProcess

It's simply one-shot command execution, using (only some part of) the
ValgrindProcess machinery that just happens to also to wrap a process
is conceptually different from ValgrindProcess that "is" the
valgrind-with-debuggee entity (and an unneeded dependency)

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

src/plugins/valgrind/valgrindrunner.h

@@ -76,17 +76,17 @@ public:
 
 signals:
     void logMessageReceived(const QByteArray &);
-    void extraStart();
 
     void processOutputReceived(const QString &, Utils::OutputFormat);
     void processErrorReceived(const QString &, QProcess::ProcessError);
-    void started();
+    void valgrindStarted(qint64 pid);
     void finished();
     void extraProcessFinished();
 
 private:
     bool startServers();
     QStringList memcheckLogArguments() const;
+    void onValgrindStarted(qint64 pid);
 
     void processError(QProcess::ProcessError);
     void processFinished(int, QProcess::ExitStatus);