(PUP-3136) Fix Intermittent Acceptance Test Failures

It was discovered that when puppet attempted to start apache the
provider would say that it was stopped even though it was starting. On
agents where a puppet master was installed with passenger the apache
service would take longer than usual to start lengthening the starting
process. By the time puppet tested if the service was running or not
apache would still be attempting to start causing the test to fail.

This commit replaces the apache2 package with rabbitmq since it is not
used by puppet and therefore tests down the road will not fail with us
managing it with puppet.

This commit also uses the `puppet_resource` command to utilize puppet
for checking if the packages have started or not instead of checking via
upstart on the agents.
I had some time to checkout the manifest behavior on Ubuntu this morning; it all looks good to me.  The one thing I think we can add here is the use of --detailed-exitcodes, which should ensure that puppet differentiates error states come back from the apply (a 0 or 2 being success, 4 or 6 being failure).  apply_manifest_on has some specific flags to use this; I think we'd want 'catch-failures' but checkout beaker and see.