slapos_cloud: Split edit in 2

  This is required due interacton workflow call on _setAlloctionScope.

  We could change the capacity_scope to close (so allocation worklfow order dont matter, but
  it would change the expected behaviour if we drop the interaction workflow, so it is more
  reasonable keep the existing behaviour unchanged.
21 jobs for master in 0 seconds
Status Job ID Name Coverage
  External
failed SlapOS-Master.UnitTest-Master

02:45:10

failed SlapOS.Eggs.UnitTest-Master.Python2

00:15:51

failed SlapOS.Eggs.UnitTest-Master.Python3

00:18:05

failed SlapOS-Master.UnitTest-Master

02:42:01

failed SlapOS-Master.UnitTest-Master

03:20:44

failed SlapOS-Master.UnitTest-Master

02:14:27

failed SlapOS-Master.UnitTest-Master

02:56:00

failed SlapOS.Eggs.UnitTest-Master.Python2

00:17:11

passed SlapOS.Eggs.UnitTest-Master.Python2

00:19:13

failed SlapOS.Eggs.UnitTest-Master.Python2

00:31:54

failed SlapOS.Eggs.UnitTest-Master.Python2

00:17:54

failed SlapOS.Eggs.UnitTest-Master.Python2

00:15:54

failed SlapOS.Eggs.UnitTest-Master.Python2

00:15:12

passed SlapOS.Eggs.UnitTest-Master.Python2

00:15:07

passed SlapOS.Eggs.UnitTest-Master.Python3

00:32:47

passed SlapOS.Eggs.UnitTest-Master.Python3

00:15:40

failed SlapOS.Eggs.UnitTest-Master.Python3

00:32:31

failed SlapOS.Eggs.UnitTest-Master.Python3

00:37:14

passed SlapOS.Eggs.UnitTest-Master.Python3

00:20:03

passed SlapOS.Eggs.UnitTest-Master.Python3

00:29:40

failed SlapOS.Eggs.UnitTest-Master.Python3

00:37:08