Update repo creation template to use git bundle from upstream

Previously, the repo creation project would attempt to just clone the master
branch of the puppetlabs repo of the project being built by the upstream
packaging job, and checkout the git ref that was packaged. The downside of this
is that it assumes the ref exists in the puppetlabs repo, which won't be the
case if one is packaging code that isn't checked in. This commit updates the
repo creation job to use the copy artifacts plugin, which copies the git bundle
that has been archived by the package:tar configuration of the packaging matrix
job (which will always be run, and should be a build failure if it fails). By
using the git bundle, we're again back in the world where refs don't have to be
in github/puppetlabs and we're also relying on the same code checkout as the
user.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Update packaging template to archive git bundle

Previously we would pass the git ref of the artifact "under package" to the
downstream repo creation job. The repo creation job would attempt to check it
out from the puppetlabs/$project repo, and then create repos. This doesn't work
if the ref isn't in github/puppetlabs, e.g. if one is packaging a local commit
or one in a different fork. This commit updates the packaging job to archive
the git bundle as a build artifact and forgo the REF parameter. This allows
the downstream repo creation job to pull in the git bundle via the copy
artifacts plugin, and then clone it and perform the repo creation. This
ensures the packaging repo maintains its paradigm of being able to build
artifacts that aren't necessarily checked into the the trunk. This commit also
updates the packaging job trigger to avoid passing REF in as an argument, which
no longer exists.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Update build timeout to 45 minutes from 30

Dashboard can actually take longer than 30 minutes to build, so with this
commit we bump the timeout to 45 to avoid any sort of false failure.
Enable notifications for new dynamic uber_build workflow

This commit adds another build parameter, notify, which is populated via yaml
or via the NOTIFY= environment variable. This be used to set up the dynamic
jenkins task with a notification event for the status of the job. Usage:

rake pl:jenkins:uber_build NOTIFY=moses@puppetlabs.com

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>