Fixup systemctl_swift stop/start  during the controller upgrade
Fixup systemctl_swift stop/start  during the controller upgrade

During the controller upgrade in
major_upgrade_controller_pacemaker_1.sh we use systemctl to stop
all swift services and then start them again in _pacemaker_2.sh

In the case of stand-alone swift nodes the deployer may have
used the ControllerEnableSwiftStorage: false so that only the
swift-proxy service is left on controllers (wrt swift). The
systemctl_swift function used during upgrades is changed to factor
this in.

Change-Id: Ib22005123429f250324df389855d0dccd2343feb

openstack/tripleo-heat-templates,openstack/tripleo-heat-templates,bcrochet/tripleo-heat-templates,dprince/tripleo-heat-templates,trozet/opnfv-tht,bcrochet/tripleo-heat-templates,trozet/opnfv-tht,trozet/opnfv-tht,bcrochet/tripleo-heat-templates,dprince/tripleo-heat-templates