Start making the Maemo support more generic.

This includes:
    - decoupling deploy configurations from targets (Reviewed-by: dt)
    - adding a "Generic Linux" device type
    - splitting up the Maemo deployment step into small pieces that
      can be combined in different ways (and much more easily maintained)
    - adding a new version handler for pro.user files
      (Reviewed-by: Tobias Hunger)

Also:
  - Add and use an SSH manager class for easier connection sharing.
  - Make the SSH connection parameters a fixed attribute of the connection.

src/plugins/qt4projectmanager/qt-maemo/maemorunconfigurationwidget.cpp

@@ -35,13 +35,13 @@
 #include "maemorunconfigurationwidget.h"
 
 #include "maemodeployables.h"
-#include "maemodeploystep.h"
 #include "maemodeviceenvreader.h"
 #include "maemomanager.h"
 #include "maemoglobal.h"
 #include "maemoremotemountsmodel.h"
 #include "maemorunconfiguration.h"
 #include "maemosettingspages.h"
+#include "qt4maemodeployconfiguration.h"
 #include "qt4maemotarget.h"
 
 #include <coreplugin/coreconstants.h>
@@ -313,11 +313,8 @@ void MaemoRunConfigurationWidget::handleActiveDeployConfigurationChanged()
 {
     if (m_deployablesConnected)
         return;
-    MaemoDeployStep * const deployStep = m_runConfiguration->deployStep();
-    if (!deployStep)
-        return;
-    connect(deployStep->deployables().data(), SIGNAL(modelReset()),
-        SLOT(handleDeploySpecsChanged()));
+    connect(m_runConfiguration->deployConfig()->deployables().data(),
+        SIGNAL(modelReset()), SLOT(handleDeploySpecsChanged()));
    handleDeploySpecsChanged();
    m_deployablesConnected = true;
    disconnect(m_runConfiguration->target(),