Release merge back 0.4.0

(FM-7530) - Update supported OS

…-gabccfb1

pdksync - pdksync_heads/master-0-gabccfb1

…-gbf720df

pdksync - pdksync_heads/master-0-gbf720df

pdksync - (FM-7655) Fix rubygems-update for ruby < 2.3

…-g9c815ea

pdksync - pdksync_heads/master-0-g9c815ea

Add implementations to the init task so it falls back to non-Ruby
implementations when puppet-agent isn't available. Also hide the extra
implementations from task runners that implement private tasks and task
implementations.

Previous acceptance tests were stuck on a pre-1.0 version of Bolt that
didn't support implementations and rejected the private key. We also
never test with the PE install mode from beaker-task_helper. Switch to
testing with BoltSpec::Run as the current supported test method.

(MODULES-8391) Enable implementations on the init task and hide others

(MODULES-8420) Release prep for 0.5.0

Bolt is dependent on puppet 6. The jenkins agents that run the CJC job to ship to the forge have puppet5. A pattern in modules that require bolt for testing has been established to only require bolt when the environment variable GEM_BOLT is set.

(MODULES-8420) Move to GEM_BOLT pattern

After the release prep commit to the release branch but before shipping the module a new/critical change was committed to master in order to push release to forge. This commit merges back the release prep commit to master. Will update the changelog and re-target updates at release branch.

(MODULES-8420) Merge back release branch to include change for 0.5.0

(MODULES-8420) Release prep for 0.5.0