after role deactivation stop services and remove HA resources

Same story as in https://github.com/crowbar/barclamp-keystone/pull/224

The deactivation recipes look slightly different though. 
We should compare this two PR's and determine if it makes sense to implement that functionality into a LWRP.


I don't think this is the right check for the l3 role being ha-enabled. It's (in theory) possible to deploy the l3 role on a single node of a cluster that does ha for other service. Using ```node[:neutron][:ha][:l3][:enabled]``` should be safer here.