Prior to this commit some commands in our manifest classes would not be
up to our code standards.

This commit aims to sanitise our code according to our teams best
practices.

Prior to this commit, multiple unit test cases would fail due to them
expecting commands to be run as a single String instead of arrays of
commands.

This commit aims to fix those test cases by ensuring they mimic the
structure of the commands being run on the test cases themselves.

Prior to this commit, a community member had some suggestions to further
improve the code

This commit aims to implement those suggestions after careful evaluation
and testing.

pdksync - (CONT-130) - Dropping Support for Debian 9

…_module_gems

pdksync - (PDKSync) Removal of puppet_module_gems

Hardening manifests

Removal of the block as no version is currently supported

…pport

pdksync - (CONT-189) Remove support for RedHat6 / OracleLinux6 / Scientific6

Prior to this PR, this module contained instances of Facter::Util::Resolution.exec and Facter::Util::Resolution.which, which are deprecated.
This PR aims to replace these exec helpers with their supported Facter::Core::Execution counterparts.

This PR:

- Replaces all Facter::Util::Resolution instances with corresponding Facter::Core::Execution exec helpers

Fixed Spec Test Failures

…ed_facter

* Update package naming to differentiate between minor versions

* adjust tests to new archive names

* adjust tests to new archive names

Prior to this commit, and after the work performed in
[Hardening manifests](#525),
the minimum puppet version requirement was expected to be raised up to
6.24.0 to meet logic requirements.

This commits aims to fix the missing bump.

(CONT-263) Update minimum required puppet version

Release prep v9.0.0