…module used in rpm based platforms

(PA-5954) Add Amazon linux to install the 'cronie' (instead of cron) module used in rpm based platforms

(PA-5575) Add Amazon to display support in Puppet forge

This commit updates this module from PDK template 2.7.1 to 3.0.1.

In addition to the boilerplate changes, this also:

- Updates the "auto release" GitHub Action to "release prep," reflecting
  upstream change (puppetlabs/pdk-templates@c3f57b7).
- Removes the github_changelog_generator and concurrent-ruby gems, which
  were previously needed for the release process but are no longer
  necessary in newer release processes in the PDK template.
- Changes "Darwin" to "macOS" in the metadata.json.

Update to PDK template 3.0.1

This commit removes logic that skipped tests on older agents that are no
longer supported.

The assert_no_match method in Beaker was long deprecated then eventually
removed altogether in voxpupuli/beaker@6282311

This commit updates assert_no_match to refute_match.

Previously in Beaker, you could use standalone stdout and stderr methods
to access output from remote machines.

These methods were deprecated in 2013 with voxpupuli/beaker@28b2510 and
dropped entirely in voxpupuli/beaker@73a31c7.

This commit removes these methods from Beaker tests in favor of calling
stdout and stderr methods on Result objects.

Update deprecated Beaker methods

Stop using legacy facts

Previously, when running with beaker 5 and latest beaker-puppet, tests failed
with:

    cannot add defaults of type pe for host redhat7-64-1 (add_pe_defaults_on not present)

The error came from beaker-puppet when it tried to configure the host as a PE
agent[1].

The root cause is beaker defaults its options to `pe`[2]. When `beaker-puppet`
calls the `configure_type_defaults_on` method, it calls the appropriate
`add_<type>_defaults_on` method. This works when using beaker 4 as `beaker-pe`
is pulled in as a dependency and its `add_pe_defaults_on` method[3] is included
into the tests.

However, when running with beaker5, beaker-pe is not loaded, so the method is
undefined. It appears beaker-puppet_install_helper is responsible for the
whether beaker-pe is loaded or not, but only when using
beaker-puppet_install_helper 0.9.4.

Since these tests don't actually depend on PE, drop beaker-pe, require
'beaker-puppet' directly (so the install_from_build_data_url method exists) and
configure the host type directly.

[1] https://github.com/puppetlabs/beaker-puppet/blob/7175b5c1acb5cddb3a31ddcc114f09cddd3b83d0/lib/beaker-puppet/install_utils/puppet_utils.rb#L167
[2] https://github.com/voxpupuli/beaker/blob/c61ee381d3801bad70989d9b3cbf970771e6f330/lib/beaker/options/presets.rb#L139
[3] https://github.com/puppetlabs/beaker-pe/blob/3bfe913b8d57c805cc0c51ae899fff174224d5f5/lib/beaker-pe/install/pe_defaults.rb#L93

Update beaker dependencies in .sync.yml

  beaker 5.x
  beaker-abs 1.x
  beaker-puppet 3.x

Beaker5

No version of beaker-puppet is compatible with Ruby >= 3.2 because of
taint functions. Because beaker-puppet specifies that it cannot run on
Ruby > 3.1 in its gemspec, when you run bundle install on newer
Rubies-even when excluding the Gem group to which beaker-puppet
belongs-Bundler errors.

This commit updates the Gemfile to only list beaker-puppet if Ruby is
less than 3.1.0.

This commit updates the Rakefile to only attempt to use Vox Rake tasks
if the voxpupuli-acceptance gem is installed.

This commit comprises minor documentation updates as flagged by Puppet
Strings. This includes:

- Moving the Japanese README to the root of the project (YARD does not
  know how to parse a readmes directory).
- Add a minimal description to the crontab provider.

Release prep housekeeping

Release prep v1.3.0