Only set WP_DEBUG locally

In a staging environment, we don't want WP_DEBUG enabled.

See #343
Define pub/twentyfourteen as WP_DEFAULT_THEME for unit tests
Merge pull request #353 from xwp/feature/default-theme

Define pub/twentyfourteen as WP_DEFAULT_THEME for unit tests
Fix invalid crontab entries

Every 30 hours isn't a valid entry
Merge pull request #357 from danielbachhuber/patch-4

Fix invalid crontab entries
Add entries in the minute column
Merge pull request #358 from danielbachhuber/patch-5

Add entries in the minute column
Add vagrant and ubuntu users to www-data group.

See #359
Change PHP process owner to www-data

See #359
Change /srv/www owner to www-data:www-data outside Vagrant.

See #359
Set web directory ownership in the nginx module

See #359
Merge pull request #360 from Automattic/issue-359

Remove vagrant user outside Vagrant
Merge pull request #348 from Automattic/issue-343

Only set WP_DEBUG locally
Add Packer template

We're going to distribute an AMI on AWS. This adds the Packer
template that we'll use to generate it.
Remove dependency on vagrant user.
Use WP module to install WP

Instead of manually running the wp-cli command, we should use
the WordPress module. We couldn't do this in the past because
is-installed was broken. This appears to be fixed!

fixes #43
Read Puppet templates from /srv instead of /vagrant

As of Vagrant 1.7, the /vagrant directory doesn't exist if there
are other shares of `.`

Fixes #354
Merge remote-tracking branch 'remotes/origin-vip/master'

Conflicts:
	puppet/manifests/sections/wp.pp