Runit should wait for drdb before starting backend services

Background info here: https://chef.leankit.com/Boards/View/111432846/146112858

In short the backend services have historically tried to start before the HA backing store was mounted and then got horribly confused.  This prevents the backend ha services from starting until the backing datastore is mounted and passing basic tests.

It relies on the `ha_backend_storage status` command and is therefore backing storage level agnostic.

I tested it by hand on standalone (ensuring it built correctly and pedant passed) and with HA on EC2 (ebs) in which I ensured the services started correctly (with pedant tests passing) and then changed the backend storage status script to return 1 and saw that the services were waiting.

Wilson run: http://wilson.ci.opscode.us/job/chef-server-12-trigger-ad_hoc/231/
If others are wondering how this works, it is because we start runsvdir with /opt/opscode/embedded/bin/runsvdir-start which is created as part of our omnibus build of runit using the following template:

    https://github.com/opscode/omnibus-software/blob/master/config/templates/runit/runsvdir-start.erb#L18

which puts `/opt/opscode/bin` in the PATH.  `source` will do a path lookup whenever its argument doesn't include "/"