Revert "Add initial support for building in a RHEL 7 mock"

This reverts commit b471b9d2a37ca10d0d20c294e813b5a46e6cabd9.
Merge pull request #2353 from melissaanne/maint/stable/revert-el7-mock

Revert "Add initial support for building in a RHEL 7 mock"
(PUP-751) Check for reparse once per compile

Previously, whenever the known_resource_types
(Puppet::Resource::TypeCollection) was retrieved from the
environment it would check if there were any files that needed to be
reparsed. If any files needed a reparse, then the entire TypeCollection
was thrown away and redone.

In most cases the reparse check did not need to touch the filesystem
because the Puppet::Util::PeriodicWatcher would return a cached result
until the filetimeout had expired. Unfortunately the check was done so
often that the overhead of simply checking if enough time had passed
caused it to take a considerable amount of time.

This changes it so that the environment's known resource types are only
recalculated if the new check_for_reparse method determines that it
should. The new method is only called at the beginning of a compile and
so the files will never be checked while a compilation is being
executed.
(maint) Backport benchmarking from 3.5 to 3.4.2

This backports the bechmarking from Puppet "3.5.0" (i.e. master)
to 3.4.2 and modifies the many_modules benchmark to not use lookup
to get the "benchmarking" environment.
(maint) Make benchmark:defined_types work on 3.4.2

This changes the use of lookup to creating an Environment.
(maint) Set required conf parameters to make benchmarks do something

The backport did not consider that environments needed to be configured
differently than for the new env support in 3.5.
Merge pull request #2356 from hlindberg/maint_add-benchmarking-to-stable

(PUP-751) Add benchmarking to stable
Merge pull request #2355 from zaphod42/issue/stable/pup-751-backport-performance-fix-to-stable

(PUP-751) Check for reparse once per compile
(PUP-1473) Fix issue with UTF-8 in user comments

GH-1943 included a change to munge the comment property on the user
type so that it gets encoded as ASCII-8BIT. This was to allow the comment
property to handle UTF-8 values as existing values are read as ASCII-8BIT.

Originally the change called `force_encoding` to force the encoding to
ASCII-8BIT. This method does not actually attempt to encode the string, it
only changes the string's associated encoding. It was suggested during code
review that a call to `encode` should be used instead. However, calling
`encode` will fail if the string has UTF-8 characters that cannot be
represented in ASCII-8BIT.

As we desire the comment property to be treated as a squence of bytes in
this case, we should be calling `force_encoding` instead of `encode`.
(maint) Fix spec for UTF-8 strings in user comment properties

The first problem with this spec is that it wasn't actually
being run due to an always false "if" clause.  It was checking
for `String` responding to `encode`, but `encode` is an instance
method.  `method_defined?` should have been used instead.

The second problem with this spec is that the test value did not
contain any non-ASCII characters.  If it had, it would have caught
the bug described in PUP-1473.  Added a non-ASCII character to test
for regressions.
Merge branch 'pup/1473' into stable

* pup/1473:
  (maint) Fix spec for UTF-8 strings in user comment properties
  (PUP-1473) Fix issue with UTF-8 in user comments

This closes GH-2360.
(packaging) Update PUPPETVERSION to 3.4.3
(PUP-1677) Fix tests for PE compatibility

1) A SLES compatibility issue was fixed

2) the reset_agent_ssl helper does not work on PE. A test which relied
on it would fail because it used duplicate certificate names. That
test was updated to use unique certificate names for each cert
request, to avoid duplicate cert issues.
Merge pull request #2371 from branan/fixup_tests_for_pe

(PUP-1677) Fix tests for PE compatibility