When the replica is upgraded and PuppetDB sync doesn't complete within
15 minutes, the upgrade command exits with exitstatus 11. This should
not be a condition in which the upgrade plan fails; the upgrade plan
should proceed forward in this case. There are many reasons why
PuppetDB sync might not complete quickly, but it's not a reason not
to continue upgrading the compilers. Upgrading the remaining
compilers will result in a more stable deployment than not upgrading
them, whatever the reason for PuppetDB sync being incomplete/slow.

Code 11 means "PuppetDB sync in progress but not yet complete". We don't
want to abort upgrade on this code.

Commit also refactors task to make it easier to unit test.

Print better data when something goes wrong. Example: when the token
used to connect to the orchestrator is not permitted to perform the
requested operation.

This feels more user-defined and unlikely to be affected by future Bolt
product changes, compared to relying on whether or not a tty is present.

Infra upgrade improvement

This requires puppetlabs-stdlib version 6.5.0 or newer.

This allows us to ensure the data we need, but preserve any user data
that may have been set, on the node groups we manage.

Add bolt_version function and use it in plans

Use node_manager's new purge_behavior parameter

  * Previously there was not any unit tests for
    validate_version function.  Additionally, the function
    was updated to return a Boolean unless the unsupported
    version is identified.  This return value, while not used
    in plans helps with unit testing.

Adds testing for validate_version

fix documented parameters for peadm::install plan

This prevent the following installation error when the source Bolt host runs a non-US locale:
`failed to call refresh: invalid byte sequence in US-ASCII`

Added modules to bolt-project. Removed Puppetfile

Ensure locales are set to en_US.UTF-8 for install

PE 2021.0 support

There is a Bolt bug where if tty is true, apply blocks won't work in
plans. That will get fixed but in the meantime, removing this from the
doc example just in case in the time between now and the bug being fixed
somebody copy-pastes the config into something. We don't want them to
get tripped up by something like that.

Now that WhatsARanjit has released a new version of node_manager

Metadata and Changelog updates

Release 2.5.0