Installation of dpkg in debian is unnecessary

How would one even install dpkg through package {} without dpkg
installed?...
Galaxy now uses tool_conf.xml.sample directly

According to the comment in the sample file, if tool_config_files is not
set and tool_conf.xml doesn't exist, Galaxy defaults to using
tool-conf.xml.sample directly. The tool-conf.xml file is not
automatically copied from tool_conf.xml anymore.

Consequently, default tool_config_files to look in tool-conf.xml.sample
instead of tool-conf.xml. This still doesn't reproduce the claimed
default behavior, in that if a tool-conf.xml is created, it will not be
used. Nevertheless, the expectation is that only puppet will be used to
manage the instance, so this is not an issue.

This fixes Galaxy failing to start with:
ConfigurationError: Tool config file not found: ./tool_conf.xml
Add unless to manage_tools run

To avoid having a resource "change" unnecessarily.
Remove galaxy::instance

This file is not used anymore. I concluded this because it had a
reference to a type that does not exist at this point:
galaxy::first_run.
Remove unused galaxy.debian-init.erb
Rename universe_wsgi.ini config/galaxy.ini

In line with changes in Galaxy.
Remove galaxy::common_startup

Most likely not needed anymore. Galaxy ships with an updated version of
the script and it's already called from the scripts that need it.
Only run create_db.sh when data source changes

Avoids being notified of an updated resource constantly; helps
performance.
Avoid spurious notifications of changing branches
Config files have moved to config/
Support status on debian init script