The Checkout GitHub Action v3 uses Node 16, which hit end-of-life on
September 11, 2023.

This commit updates all instances of the Checkout Action from v3 to
v4.

(PA-5804) Update Checkout GitHub Action

This commit updates the static code analysis GitHub Actions workflow
from using a copy in this repository to a resuable copy in the Phoenix
team centralized GitHub Actions repository.

In addition, this removes the commits Rake task as it is no longer used
in the reusable version of this workflow.

This commit adds a GitHub Actions workflow to export issues from GitHub
into Jira.

(PA-5395) Issues housekeeping

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

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

In addition to the boilerplate changes, this commit 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.

Update to PDK template 3.0.1

Co-authored-by: Josh Cooper <737664+joshcooper@users.noreply.github.com>

Stop using legacy facts

This commit updates .sync.yml and Gemfile to use newer beaker dependencies:
beaker 5.x
beaker-abs 1.x
beaker-puppet 3.x

This commit also removes beaker-pe.

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

Commit originally from joshcooper/puppetlabs-cron_core@d456d2a

(PA-5781) Use Beaker 5

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.

Release prep housekeeping

Release prep v2.1.0