Use an upstart job to manage mcollectived

Use an upstart job to manage mcollectived

sys v init scripts are inherently racy since creating a PID file takes
a while. In particular collectived needs about 0.6 seconds to daemonize
itself and create its PID file. If the service gets restarted in this
interval the second instance of the daemon gets started without stopping
the previous one. Apparently mcollectived gets restarted very often
during the final phase of IBP. Hence get rid of sys V init script and
use an upstart job to manage mcollectived.

openstack-ci-packtest-deb is expected to fail without the corresponding
nailgun patches:
 https://review.openstack.org/186027
 https://review.openstack.org/186028

Related-Bug: #1454741
Merge-After: https://review.openstack.org/186027
Change-Id: I70d75f77e96447ae20034e170385b46484f51d5e