ControlledDynamicWebAppCluster: add SERVICE_STATE

- Was seeing cluster getting "on-fire" icon in web-console sometimes.
  Was probably caused by propagating SERVICE_STATE from cluster
  and SERVICE_UP from load balancer - if values didn't agree then 
  would fail.
- However, before realising that (!) I fixed it by adding SERVICE_STATE
  explicitly in start/stop, in much the same way as AbstractApplication
  does it.
DynamicCluster: fix serviceState order

- Change order of setting SERVICE_STATE and SERVICE_UP. If set 
  RUNNING before serviceUp=true, then web-console infers that as
  a failure and can mark entity as in flames.
Merge pull request #1316 from aledsage/fix/ControlledDynamicWebAppCluster-onfire-transient

Fix ControlledDynamicWebAppCluster transient on-fire