Add `rake run` task to the two ldap containers

Without this patch there is no easy way to start each of the systemd and
lightweight ldap containers.  This patch addresses the problem by adding
a rake run task to each build context.
Add build and run tasks for a jenkins systemd container

Without this patch there is no jenkins container build procedure.  This
is a problem because we need to build a jenkins base image prior to
running the jenkins service in a container.  This patch addresses the
problem by creating a Dockerfile and rake tasks to build the jenkins
base image and run the image.

The build phase contains the expected error of not being able to manage
the Service[jenkins] resource:

    Error: Could not start Service[jenkins]: Execution of '/usr/bin/systemctl start jenkins' returned 1: Failed to get D-Bus connection: No connection to service manager.
    Wrapped exception:
    Execution of '/usr/bin/systemctl start jenkins' returned 1: Failed to get D-Bus connection: No connection to service manager.
    Error: /Stage[main]/Jenkins::Service/Service[jenkins]/ensure: change from stopped to running failed: Could not start Service[jenkins]: Execution of '/usr/bin/systemctl start jenkins' returned 1: Failed to get D-Bus connection: No connection to service manager.
    Warning: /Stage[main]/Jenkins/Anchor[jenkins::end]: Skipping because of failed dependencies

Despite the error, jenkins runs in the resulting systemd enabled
container using `rake run`.
Cache packages in the systemd base image

Without this patch the build phase for the jenkins container takes a
long time because large packages need to be installed each time the
container is built.  This patch addresses the problem by installing the
packages in the centos7vps base image which will speed up puppet.
WIP Make Service[jenkins] work in `docker build`

Without this patch puppet does not successfully complete during the
`docker build` phase of the jenkins container.  This is a problem
because there should be no configuration errors present in the puppet
results.

The root cause of the problem is Puppet trying to manage the
Service[jenkins] when systemd is not running and operational.

This patch addresses the problem by overriding Class[jenkins::service].
The original module is modified from upstream because it specifically
guards against modifying a private class and uses resource class
declaration syntax which is problematic with class overrides.

REMAINING WORK:

 * Figure out how to start the Java service natively without having to
   start systemd.