Custom fragments in apache::vhost
For the time being, the apache::vhost defined type is somewhat
inflexible with certain portions of configuration. Until the proper
concat fragments are added, things like rewrite rules/conds, extra
directories, and more cannot be adequately managed.

This commit allows users to define either one, or an array of "custom
fragments" to be added to the end of the configuration.
Documentation for custom_fragment parameter
Add $custom_fragment_params to apache::vhost
The custom fragment templates run in the scope of the apache::vhost
type. In Puppet 3.x dynamic variable lookups are no longer supported.
This will prevent extra data from being passed to the custom fragments.

This commit adds the $custom_fragment_params parameter to the apache::vhost
type to allow users to pass data through to apache::vhost for use by the templates.
This methods expects users to pass the information through as a hash.
Update changes based on #24

This commit:
- Causes `custom_fragment` to accept static content instead of template
  paths
- Removes `custom_fragement_params` because it is no longer used.
- Changes a little of the template logic to match the other fragments

Conflicts:
	manifests/vhost.pp
Adding spec tests for custom_fragment