Split repo file generation, shipping, and retrieval into separate tasks

Currently repo config file generation generates new repo configs at runtime on
the local station. This is not optimal because it means to get repo configs you
have to have $project cloned with the packaging repo to get repo configs. This
commit changes the workflow by creating the repo configs in one step, shipping
them to a static (and predictable) location on the distribution server, and
modifying the current rpm_repo_configs and deb_repo_configs to just retrieve
the stored configs on the server. This allows us to just wget the configs since
we know what their location will be. We can generate the configs and store them
on the distribution server as a post-repo generation step.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Create and ship repo configs as part of repo creation

Now that we generate configs locally but store them on the distribution server,
we have to get them there. We could do it manually, or it could just be part of
the repo creation process. I'm opting for the latter.

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