workernode and primproc should not be started on newly added PMs

Build tested: 1.1.4-1

Started with a 1um2pm stack, I performed the following steps to add two PM modules:

1. Adddbroot (2)
2. Addmodule (2)
3. altersystem-enablemodule (s)
4. assignDbrootPmConfig

The newly added PMs have the following status

ProcessMonitor pm3 ACTIVE Tue Apr 17 20:44:03 2018 14725
ProcessManager pm3 MAN_OFFLINE Tue Apr 17 20:42:45 2018
DBRMControllerNode pm3 COLD_STANDBY Tue Apr 17 20:47:15 2018
ServerMonitor pm3 MAN_OFFLINE Tue Apr 17 20:42:45 2018
DBRMWorkerNode pm3 ACTIVE Tue Apr 17 20:47:31 2018 14885
DecomSvr pm3 MAN_OFFLINE Tue Apr 17 20:42:45 2018
PrimProc pm3 ACTIVE Tue Apr 17 20:47:42 2018 14901
WriteEngineServer pm3 ACTIVE Tue Apr 17 20:48:05 2018 14941

ProcessMonitor pm4 ACTIVE Tue Apr 17 20:44:06 2018 14587
ProcessManager pm4 MAN_OFFLINE Tue Apr 17 20:42:45 2018
DBRMControllerNode pm4 MAN_OFFLINE Tue Apr 17 20:42:45 2018
ServerMonitor pm4 MAN_OFFLINE Tue Apr 17 20:42:45 2018
DBRMWorkerNode pm4 ACTIVE Tue Apr 17 20:47:36 2018 14646
DecomSvr pm4 MAN_OFFLINE Tue Apr 17 20:42:45 2018
PrimProc pm4 ACTIVE Tue Apr 17 20:47:43 2018 14662
WriteEngineServer pm4 ACTIVE Tue Apr 17 20:48:06 2018 14702