QmlProfiler: Move unrelated code out of QmlProfilerClientManager

The client manager should not be bothered with details of QML events,
but rather just connect the client, the model manager, and the state
manager.

Change-Id: Iec4499f8441a06d4ef5cbcf7bfe23da6f5e7f239
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

src/plugins/qmlprofiler/qmlprofilerclientmanager.h

@@ -59,14 +59,13 @@ public:
     void setModelManager(QmlProfilerModelManager *m);
     void setFlushInterval(quint32 flushInterval);
 
-    bool aggregateTraces() const;
-    void setAggregateTraces(bool aggregateTraces);
-
     void setRetryParams(int interval, int maxAttempts);
     void retryConnect();
     void connectToTcpServer();
     void startLocalServer();
 
+    void stopRecording();
+
 signals:
     void connectionOpened();
     void connectionFailed();
@@ -89,8 +88,6 @@ private:
     int m_maximumRetries = 50;
     int m_numRetries = 0;
 
-    bool m_aggregateTraces = true;
-
     void disconnectClient();
     void stopConnectionTimer();
 
@@ -100,12 +97,6 @@ private:
 
     void logState(const QString &);
 
-    void qmlComplete(qint64 maximumTime);
-    void qmlNewEngine(int engineId);
-
-    void profilerStateChanged();
-    void clientRecordingChanged();
-
     void createConnection();
     void connectClientSignals();
     void disconnectClientSignals();