Valgrind: Quickfix for remote execution.

Lots of stuff is still horribly broken due to the weird confusion
between local/remote and "has project"/"does not have project" that
crept in at some point, but this at least makes remote, project-specific
memcheck work again.
Still broken:
    - Remote callgrind
    - All remote valgrinds for external projects.
    - Local remote valgrind is not even available (anymore), as
      the respective menu entries have disappeared at some point.

Change-Id: Iae6b60a0508d1b1b64fd0e0e5f776ea2c2e23598
Reviewed-by: hjk <hjk@theqtcompany.com>

src/plugins/valgrind/valgrindprocess.cpp

@@ -42,6 +42,7 @@ ValgrindProcess::ValgrindProcess(bool isLocal, const QSsh::SshConnectionParamete
     : QObject(parent),
       m_isLocal(isLocal)
 {
+    m_isLocal = sshParams.host.isEmpty();
     m_remote.m_params = sshParams;
     m_remote.m_connection = connection;
     m_remote.m_error = QProcess::UnknownError;

src/plugins/valgrind/valgrindruncontrolfactory.cpp

@@ -81,8 +81,6 @@ RunControl *ValgrindRunControlFactory::create(RunConfiguration *runConfiguration
             qWarning() << "Cannot open port on host for profiling.";
             return 0;
         }
-        connection.connParams.host = server.serverAddress().toString();
-        connection.connParams.port = server.serverPort();
     } else {
         connection.connParams = device->sshParameters();
     }