Separate scripts to be included on puppetmaster

We shouldn't make the assumption that foreman runs on the same hosts as the
puppetmaster.
So this patch separates the scripts that are to be installed on the
puppetmaster (enc & report script) into the class foreman::puppetmaster
that can be added to the puppetmaster.

Change-Id: I89b0439d18c1e4032b64c12c337de51958e7f1ab
Enable choice of repo (for Debian)
Don't overwrite new config.ru with old link
Merge pull request #3 from GregSutcliffe/repo

Enable choice of repo (for Debian)
Don't mess with the database on nightly
Merge branch 'master' of github.com:theforeman/puppet-foreman
Merge pull request #2 from dalen/master

Separate scripts to be installed on puppetmaster from those that are installed on foreman server
Fixes:

* Include params in config/enc.pp as I include this on puppetmasters
  that do not run foreman.
* Fix a typo in the external_node.rb.erb template.
* Change latest to present.
Parametrize params so that they can be overwritten

Taking the approach from puppet-puppet that allows reuse the manifests by
overriding the params like:

    class customized_foreman {
      class { '::foreman': passenger => false }
    }
Use class {} instead of include
Parameterize `foreman::install::repos` attributes

It makes it easier to share the repo among different modules, such as
`foreman_proxy`.
Prioritize included classes in init.pp
Allow to use custom repos instead of the predefined ones
Add $package_source to class params to allow foreman and foreman_proxy classes access
puppet-lint fixes
Merge pull request #6 from ekohl/master

puppet-lint fixes
Convert repo to a define
Fix repo always using Debian stable, ignoring
Fix default package source, and cover testing in config.ru fix
Added new yum repos for 1.0