(PUP-3462) Add the key 'calling_class_path' which is 'calling_class' with '::' by '/'

This enables to have the class hiera yaml files in directories and enables to
have class based hiera data on windows which does not allow ":" in path names.
(PUP-3063) Remove client certificate expiration check

This is a follow-up to PUP-3031.  The code that we were using
to issue a warning about expiration dates of client certificates
was in a pretty heavily-frequented path, was expensive, and
did not account for differences between the various web
servers that we might be running in.  We decided that it would
be better to provide a CLI tool for this, rather than having
it be something that is triggered on each HTTP request.

The design / scope for the CLI tool is not fleshed out yet,
and we did not want to leave orphaned code in the source tree
until that happens, so the code is just being removed for now.
(PUP-3063) remove certificate expiration warnings

This commit deletes the 'certificate_expiration_warning' setting and the
'near_expiration?' method which used this setting.
(PUP-3247) Remove trigger_string method

Previously, our vendored task scheduler code defined a method that if
called would never work. This is because it would try to return the
`trigger` local variable, but it was never defined, and so would call
the `#trigger` method instead, and that requires one argument for the
index.

This commit just removes the method since it's never used in puppet.
Merge pull request #3246 from joshcooper/ticket/master/PUP-3247-remove-trigger-string

(PUP-3247) Remove trigger_string method
Merge pull request #3175 from vinzent/calling_class_path

(PUP-3462) Hiera scope: add the key 'calling_class_path'
(PUP-3277) Set selinux context for new acceptance test environments

The acceptance environment_utils currently backup existing $confdir
files and copy in test environment files created in /tmp.  These test
files may have a different selinux context than $confdir, which can
result in agent -t runs coming back with selinux context changes and an
unexpected exit code of 2. Rather than just assume that all agent runs
may have resource changes, the helper instead sets $confdir's context
for the test files once they have been copied in (if selinux is
enabled).
Merge remote-tracking branch 'upstream/stable'

* upstream/stable:
  (PUP-3277) Set selinux context for new acceptance test environments
(maint) Allow domain to specified when re-running pe acceptance
(PUP-3277) Allow resource changes in ticket 5477 test

Reports ending up in the /var/log/pe-puppet-dashboard/failed_reports
directory during pe tests runs had an seluser context that differed from
that which the puppet_enterprise module would manage in subsequent agent
runs. This was interaction between the
acceptance/tests/allow_arbitrary_node_name_fact_for_agent.rb from
which the reports were being generated, and this ticket_5477 test which
was exiting with a 2 because of the selinux context changes in the
failed_reports directory. I'm not positive why these two particular
tests happen to have this interaction. The allow_arbitrary_node_name
test is the first to run after installation. The ticket_5477 test is not
the first test to run with an agent -t after this, but maybe the first
that ran without accepting an exit of 2. I don't see anything
wrong with the report files themselves being adjusted by the pe modules,
so I'm relaxing the acceptable_exit_codes in ticket_5477, because I have
run out of other ideas.
Merge pull request #3243 from KevinCorcoran/PUP-3063/delete-cert-expiration-code

PUP-3063: remove certificate expiration warning