Upstart: install inotify-tools only once (avoid CHEF-3694 warning).

[jperville]

This PR avoids the resource-cloning (CHEF-3694) warning that triggers when deploying more than one container as upstart services.

Symptoms of the problem:

==> default: [2014-11-18T08:35:44+00:00] WARN: Cloning resource attributes for package[inotify-tools] from prior resource (CHEF-3694)
==> default: [2014-11-18T08:35:44+00:00] WARN: Previous package[inotify-tools]: /tmp/vagrant-chef-3/chef-solo-1/cookbooks/docker/providers/container.rb:490:in `service_create_upstart'
==> default: [2014-11-18T08:35:44+00:00] WARN: Current  package[inotify-tools]: /tmp/vagrant-chef-3/chef-solo-1/cookbooks/docker/providers/container.rb:490:in `service_create_upstart'

The reason is that the generated upstart service depends on the inotify-tools package (which must be present at compile-time since the docker_cmd commands run at compile-time); since this package is installed as a technical detail, I think that it should indeed be installed from within the docker_container LWRP as today and not in an external recipe.

[tduffield]

I like the implementation. Consider it merged.