slapos_cloud: Fix Test! Don't invoke validate directly

  By invoking validate, the interaction workflow will be kicked and allocation will be triggered. In order to control the invocation order on the test, use portal_workflow API.

master/bt5/slapos_cloud/TestTemplateItem/portal_components/test.erp5.testSlapOSCloudAlarm.py

@@ -739,7 +739,7 @@ portal_workflow.doActionFor(context, action='edit_action', comment='Visited by S
       specialise=self.hosting_subscription.getRelativeUrl(),
     )
     self.portal.portal_workflow._jumpToStateFor(software_instance2, 'start_requested')
-    software_instance2.validate()
+    self.portal.portal_workflow._jumpToStateFor(software_instance2, 'validated')
     self.tic()
 
     self.assertEqual(None,
@@ -956,9 +956,10 @@ portal_workflow.doActionFor(context, action='edit_action', comment='Visited by S
       specialise=self.hosting_subscription.getRelativeUrl(),
     )
     self.portal.portal_workflow._jumpToStateFor(software_instance2, 'start_requested')
-    software_instance2.validate()
+    self.portal.portal_workflow._jumpToStateFor(software_instance2, 'validated')
     self.tic()
 
+
     self.assertEqual(None,
       self.software_instance.getAggregateValue(portal_type='Computer Partition'))