Allows Puppet Agent to be installed on both Rocky Linux and AlmaLinux through the install.sh task.

(IAC-1751/IAC-1753) Add Rocky and AlmaLinux support to the install agent task

puppet-agent module

(MODULES-11192)(MODULES-11168) Add AlmaLinux and Rocky to the puppet-agent module

When a non-AIO Puppet version is installed (e.g. on FreeBSD where Puppet
packages are maintained by the FreeBSD community), Bolt is unable to
detect the version of Puppet.

If no evidence of the presence of Puppet is found at the AIO locations,
check if a `puppet` command is found in the $PATH, and if so, run it
with the `--version` parameter to get the version of Puppet.

Allow detection of non-AIO Puppet

* Add fact-limit configuration options to list.

There are two fairly new options which go in puppet.conf.

Add more missing configuration options

The dockerfiles are only used for iterative development to test upgrades.

(MODULES-11238) Bump centos base docker image

Previously, any Darwin 11 machine that used a facter version older than
4.1.1, and tried to update the puppet-agent version using the
puppetlabs-puppet_agent module, would recieve a badly generated URL.

This happened because the `productversion_major` fact also included the
minor version.

…t-darwin

(MODULES-11214) Wrong url generated for darwin 11

save `commits` and `gen_nodeset` in `rakelib`

adapt spec helpers to keep the existing setup

Adding back gems needed to run acceptance tests
Delete not needed file `spec/default_facts.yml`

* save existing changelog to HISTORY.md
* configure changelog generator to generate new entries
    starting with 4.9.0 tag
* pin octokit to 4.21.0 since we hit the issue at octokit/octokit.rb#1391
* pin async to ~> 1.30 otherwise async 2.0.0(needs ruby >=3.1.0) is wrongly selected by
    bundler on jenkins while running with ruby 2.7.1

(maint) pdk convert

(maint) Add phoenix to CODEOWNERS

Release prep v4.10.0