Try to reduce the number of `if` statements in code, and remove the need
to specify `ha` as a Boolean plan parameter. Instead, do HA if HA
systems are specified, and don't if they aren't.

Newer versions of Bolt don't print anything to the screen when running
the notice() function. The replacement is out::message().

So that when/if no HA systems are passed, the manifest works correctly.

This was a problem in the shell wrapper, not the Puppet code itself.

Wasn't functionally necessary but this is more correct

Not sure where this got lost, but it's a non-operational task without
it...

The database systems need to use the installer to set up, but the
replica doesn't.

This identifier can help user code know whether or not a node is a
master, has resources like Service[pe-nginx], and so make intelligent
decisions about whether or not to apply addendum configuration that
depends on a node being a master.

(SLV-365) Update the install, configure, and upgrade plans in the pe_xl module to make ha optional

Upgrades can now be completed from anywhere as long as it
doesn't rely on PCP transport

General cleanup. New features have been added so a version bump is about
due.

This commit updates the plans, tasks, and templates to make the
setting of `puppetdb_database_host` optional.  Without this setting,
a "large" environment will be deployed where PuppetDB resides on the
master.

This commit adds a document for using the pe_xl module to deploy
a "PE Large Architecture".  An architecture diagram for the supported
deployment is included for clarity.  Currently, deploying the HA
version of the Large Architecture is not supported by the tooling.

This commit makes some UX changes to varible names to new "target"
variables in use, now that there are several of them. The changes aim to
make each "target" clearly relate to the original input variable it was
based on.

This commit also tries to smooth over the epp template quoted string
issue. It makes the puppetdb_database_host parameter to the template
optional, so that undef is permissable to pass.

SLV-366 Make external database host optional

It was unused, and wouldn't have worked even if somebody did pass a
value to it.

Updated the code_manager.json file to match actual usage. Specifically,
the action param was listed as type enum, but in the configure plan we
were already using a variable in invoking it such that the action didn't
match any of the enum values. So now it's just a string.

Fixes #19

Make use of Puppet language #protocol object methods to check a Target's
transport. This obviates the need to include a Ruby langugage function
for accessing the internal #target method.

Removed local:// dependency for upgrades

This should be updated later to a Solutions Architects Github group,
assuming we create one.

The puppet-syntax gem doen't deal well with Bolt Plans. Add a line to
the Rakefile to configure it to stay out of the plans directory for now.

Update the metadata.json file with the new module namespace, moving from
"reidmv" to "puppetlabs"

Provide parameters that match 80% of users' experience configuring
code-manager. Namely, add r10k_remote and r10k_private_key settings.

Observationally:

  - We ALWAYS want to configure Code Manager
  - We ALWAYS want the private key location configured the same
  - We can use pe_conf_data to override anything if we need to
  - We don't want magic

To that end, this commit simplifies the r10k private key input to
require that the key content is supplied OR the path to a local file
containing the key. The two parameters are different, and mutually
exclusive.

Added ability fo fully bootstrap Code manager

This cleans up the interface a bit, optimizing it for the 90% use case.

This helps clarify the intended user interface classes, currently
provision and upgrade.

Previously, it did not include module deployment.

V4

Using `hostnamectl --transient` doesn't *always* return the FQDN, which is what the plans are usually expecting. `hostname -f` is a more reliable way of doing this.

Fixes #22

Changed for more reliable hostname resolution

Initial refactor of pe_xl::unit::install only.

Make use of better input typing. Use get_target and get_targets in order
to operate explicitly on Target objects. This will be useful later in
configure and upgrade plans, for detecting automatically if a target is
using the local transport.

Various cleanup and compacting of code, taking advantage of the above
changes.

Removal of explicit OID numbers from csr_extension_requests.yaml. Bug
was fixed in Puppet such that this is no longer necessary.

This commit extends modern target object useage to the unit/configure
and provision plans

Namely, implement the pe_xl::target_host function to intelligently
extract the host element of a Target, iif the TargetSpec is not an empty
array. Return undef if the TargetSpec is an empty array.

This feature merge implements newer Bolt features such as data typing
based on TargetSpec, and use of Target objects by way of calling
`get_targets()` and `get_target()` on user inputs. It also rolls in
improvements to validation and bug fixes found along the way.

Previously it was just one individual