Provide a manual and scheduled workflow which fetches the latest CI
passing build of the next major PE version and does an install.

Scheduled does an Extra Large with DR deployment while manual, you can
choose from a list.

Renames the existing test-upgrade.yaml to test-upgrade-matrix.yaml and
create new test-upgrade.yaml which uses workflow_dispatch for manual
invocation.

This is the same structure used for providing install tests.

Workflows for nightly testing pre-release install

Provide automated and on-demand upgrade test

Provides a workflow which can access internal artifacts for testing the
upgrade of PE from one arbitrarily installed version to the latest
development build.

Provide changes to the peadm::upgrade plan which will make the version
parameter not required when provided a source URL from which to fetch PE
from.

Provide a schedule execution of an upgrade test from current released
version of PE to latest dev.

Provide capability to do development upgrade tests

Fix incorrect usage of env in nightly workflow

Provides a parameter in plans peadm::install and
peadm::subplans::configure which can be used to set the final state of
the puppet agent which runs on infrastructure nodes. Allows for stopped
or running states only.

New worflow for on demand validation of the peadm::add_compiler plan and
supporting other changes.

Parameter for setting final state of agents

New test for adhoc add_compiler testing

Removing redundant agent upgrade task

Versions must have been changed automatically and no longer match text correcting

Update defaults to latest minor LTS release

Adding submit csr for windows and resolved way to pass variables

Adding windows node capability

Prior to this commit, `peadm` used the `fips-mode-setup --is-enabled`
command to detect whether FIPS mode was enabled. Unfortunately,
this command does not produce a meaningful exit code. It exits
with success on RHEL 8 where the `--is-enabled` flag is invalid:

```
$ fips-mode-setup --is-enabled
Check, enable, or disable the system FIPS mode.
usage: /usr/bin/fips-mode-setup --enable|--disable [--no-bootcfg]
usage: /usr/bin/fips-mode-setup --check

$ echo $?
0
```

And exits with success when FIPS mode is disabled:

```
$ fips-mode-setup --check
Installation of FIPS modules is not completed.
FIPS mode is disabled.

$ echo $?
0
```

The end result is that if the `crypto-policies-scripts` package
happens to be installed on a RHEL node, `peadm` will assume the
node is in FIPS mode and download the wrong PE installer package.

This commit updates `peadm` to use the same method for detecting
FIPS as the PE installer: `cat /proc/sys/crypto/fips_enabled`

Sync FIPS detection with the PE installer

* adds the documentation/backup.md page

* adds the basic structure for the restore doc

* adds a note to the restore doc

* adds a 'things to consider' section for the restore plan

* adds more details to the input_file param in the restore docs

* describes how backup plan works and diff w/puppet-backup cmd

* adds a note about the expectation of get_targets to be up&running before running plans

* using David's core idea for peadm backup in description

peadm get config is a task

Update expanding.md

Prior to this commit, the finalize step of `peadm::convert` would
fail when operating on PE XL installations as the Primary Database
and Replica Database nodes do not run the pe-puppetdb or pe-puppetserver
services:

```
  The command failed with exit code 5
  STDERR:
    Failed to restart pe-puppetserver.service: Unit not found.
    Failed to restart pe-puppetdb.service: Unit not found.
```

This commit updates the convert plan to exclude the database
nodes from that service restart.

Fix XL failures in finalize step of peadm::convert

Update 2021.7.1 to 2021.7.2 for LTS

…e to bug with heredoc

Updating to reflect versions supported

Pdk2.6.1