QmlProfiler: Refactor complete() methods

The complete() methods do something more specific. We should call them
by what they do. Also, we don't need to signal the finishing of data
acquisition via a signal and most of the postprocessing can happen in
the worker thread.

Change-Id: Iae986aefb8e7e7d4327c481d7a85325bbff7fa48
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

src/plugins/qmlprofiler/qmlprofilerdatamodel.h

@@ -81,11 +81,11 @@ public:
     void setData(qint64 traceStart, qint64 traceEnd, const QVector<QmlEventTypeData> &types,
                  const QVector<QmlEventData> &events);
     void setNoteData(const QVector<QmlEventNoteData> &notes);
+    void processData();
 
     int count() const;
     void clear();
     bool isEmpty() const;
-    void complete();
     void addQmlEvent(QmlDebug::Message message, QmlDebug::RangeType rangeType, int bindingType,
                      qint64 startTime, qint64 duration, const QString &data,
                      const QmlDebug::QmlEventLocation &location, qint64 ndata1, qint64 ndata2,
@@ -94,6 +94,7 @@ public:
 
 signals:
     void changed();
+    void requestReload();
 
 protected slots:
     void detailsChanged(int requestId, const QString &newString);