name translation not working to the bash script

Due to it being more difficult to determine a correct default value for
token-file in Puppet code than in the task itself, make the token_file
argument in Puppet optional, and if not passed determine the default
value in Bash code in the task.

Make variable assignment more uniform stylistically.

Use filter() instead of reduce()

Turns out to a shell script, undef == "null". So, we have to catch that
for optional parameters.

add variable to mark a node as the replica (required for other modules to only configure webhooks on the current primary)

This is to align the directory name with the name used in other Puppet
Git projects.

For the Extra Large architecture and other new PE architectures, we are
implmenting a name change for two system roles.

+------------------------+----------------+
| Old name               | New name       |
+------------------------+----------------+
| Primary Master         | Master         |
| Primary Master Replica | Master Replica |
| Compile Master         | Compiler       |
+------------------------+----------------+

To reflect these changes, this commit changes the plan and task inputs
identifying hosts with these roles to use the new role names.

Just in case. It should be a no-op since we fully expect that this group
already exists, and that we don't need to modify its parent.

The content was just wrong. Removed most of it, left a note about the
version update from 0.1.x to 0.2.x

Or at least, remove one requirement of exec on it

Now that the puppetlabs/apply_helpers module exists to support PCP
running of the configure plan

Makes it harder to start later if systemd is struggling in vain to
recusitate it

For some reason the human names of the OIDs aren't always available
during install...

For Puppet 6 and stuff

Unfortuantely, apply() is still not quite ready. node_manager expects
and requires that some Puppet settings be available for reference in
finding the certificates to use to connect with node manager, and those
settings are not valid in the sandboxed Puppet context Bolt spins up.
Sad day.

Since this is only tested with PE 2019.0.x so far

So that the install plan works on both 2018.1 and 2019.0