(MODULES-3704) Update gemfile template to be identical

Handle array values in join_keys_to_values function

Fix spec failures on puppet 4.8

These were caused by a change in the tested error message.

Addition of 4.6 and 4.7 travis cells

Remove leading spaces

(MODULES-3829) Use .dup to duplicate classes for modification.

This function otherwise fails during `puppet preview` on Puppet 3.8.X systems.

This corrects puppet-linting error.

(MODULES-3980) Fix ipv4 regex validator

This also updates all ipv4 tests to use the same test data for better
comparability. Closes #676, #679

Fix-Originally-By: Nate Potter <nathaniel.potter@intel.com>

 This is to pin ruby version to parallel_tests

Fix incorrect environment variable name in README

The README references the environment variable `STDLIB_LOG_DEPRECATION`
while the code uses `STDLIB_LOG_DEPRECATIONS` (note the trailing S).

(MODULES-3969) Update getvar to work on ruby 1.8.7

(MODULES-3962) Rework v4 function shims to work on puppet 3.7 and 4.0.0

This is a workaround for PUP-4438 (fixed in https://github.com/puppetlabs/puppet/commit/e01c4dc924cd963ff6630008a5200fc6a2023b08, 4.1.0, 3.8.1).

It works by manually passing through the scope, instead of relying on the
InternalFunction class.

(MODULES-3961) emit more deprecation warnings

This now emits one deprecation warning for each function used (but not for each call-site). Prior to this, only a single deprecation warning would have been triggered, potentially misleading users.

Additionally this adds v4 deprecation stubs for the functions that were missed.

Mergeback

Release prep for 4.13.0

Apparently mocha 1.2.0 causes an endless hang
on spec/unit/facter/root_home_spec.rb. Forcing
an earlier version avoids this for now.

* Changelog & Thanks
* Add known issues/version compatiblity to README
* Whitespace fixes
* Update version and dependency information
* Fix issue tracker URL

Final cleanups

@keymone added information on how to reproduce his issue, so here's the
test case that would fail without his change.

This reverts commit b63862ff, as it would
only show the irrelevant first entry of the ruby stack trace. The
puppetserver log does contain the full trace information, or you can use
--strict=error to cause a hard failure when hitting a deprecation.

# Conflicts:
#	lib/puppet/functions/validate_legacy.rb

This patch updates the README to specify that the 'after' parameter
in the file_line class accepts a regular expression.

`catch` returns value of second argument to `throw`, which until 860a2761f334c964068038b3ef6853f08beb1df5 was `nil`, but now is non-falsey reason for error. short-circuit using return and eval to nil if `throw` was caught.

Type updates

(FM-5703, PUP-6717) Remove the dynamic deprecation_gen function

This was not working when the puppet master did not have the newest stdlib
version in its environment.

(MODULES-3590) Fix match_for_absence parameter