Add spec test for peadm::add_compiler

This replaces modify_cert_extensions. It supports modifying DNS
alternative names as well.

This supports the new peadm::modify_certificate plan

Previously, it could return null.

Sometimes you may want to forcibly regenerate a certificate even if it
already matches the desired state, e.g. if it is expiring soon.

This commit also fixes dns-alt-names to more concretely check for
existing status matching desired status.

This replaces the deprecated use of peadm::modify_cert_extensions

…cate

Replace plan peadm::modify_cert_extensions with peadm::modify_certificate

The .github/README.md takes precedence over README.md as being the file
which is displayed on a repo's home page, if present. This commit moves
the Github Actions readme file deeper into the .github directory to
prevent it from displaying the repo's README.md file as the
authoritative content to display on the repo's home page.

Also perform some maintenacne updates on the Github Actions readme file.

Fix GitHub README.md problem

It is not functional, but still useful as guidance for creating real
content.

Move load_balancer class to examples

Forgot to move the other two manifests related to haproxy configuration
examples to the examples directory. This commit remedies that.

This consistency lays the groundwork for creating a task which can
inspect the node groups on the primary (or replica) and return the
currently-configured PEAdm roles (primary, replica, primary-postgresql,
replica-postgresql, compilers).

The primary might be "B". This change lays the groundwork for more
robust cluster operations which don't assume that the primary is always
"A".

PEAdm creates some of its own groups, but also adjusts variables or
parameters on some existing groups. We need to use the correct names of
the existing groups, especially where the DR feature is concerned; we
don't get to rename them. So, even though "DR" is more correct these
days, we need to modify the "HA" group

Explicit A/B server param names in setup

This task can introspect an existing cluster (when run on a primary
node) and return information about how the cluster is currently
configured. This will aid in running plans that need to modify the
cluster, by reducing the amount of information the user must supply.

The task returns data about the cluster in both primary/replica form, as
well as A/B form, since different forms are useful in different
scenarios.

Improve the readability of the task, and the task description.

In the event a group doesn't exist, or a key doesn't return a value.
Don't error, just return nil for those values.

When this was refactored, the wrong defaults were given to the compiler
load balancer address variables. They should default to the A and B
*servers*, not the A and B postgresql hosts.

Realized this could be a generally useful way of understanding all
letter assignments, if we returned compilers as well.

Add get_peadm_config task

Many plans in this module are not intended to be run directly, and are
instead subplans or utility plans for internal use. This commit updates
the doc comments in the plans to indicate to Bolt that they should not
be shown or displayed when running commands like `bolt plan show`.

- Do not use color codes, as this makes the output difficult to read
  when returned by Bolt.

- Do not print <space><newline>, since this combination will prevent
  Ruby's yaml emitter from using the block form (which is easier to read
  when newlines are involved). This doesn't have an immediate impact
  since we will be seeing the error in JSON, probably, but it
  potentially heads off confusion in the future if we choose to emit
  yaml instead.

Highlight user-facing plans by hiding internal plans from bolt plan show output

Clean up output of puppet_runonce task

Same rationale as before: easier to read, cleaner output when viewed
coming back from Bolt. The color codes make it harder to read in JSON or
YAML documents.

Update docker_examples.md

Add --color=false to other puppet commands

Fix typo in brew command

Previously if a token file contained a newline, the upgrade plan would
fail. This commit fixes that bug. Token files with newlines will not
cause an error.

Fix upgrade bug for token files with newlines

A long time ago these settings were added to faciliate local development
on VirtualBox, using developer workstations. We should not provide
different memory defaults for PE installs than what is provided by PE
itself.

Additional fix: found Puppet Strings bug which prevented generating a
REFERENCE.md file. It is now possible to use Puppet Strings to generate
a REFERENCE.md.

We already had @api private, but Bolt doesn't respect that. It needs
@Private true.

Removing for now as there is no need to set peadm-coded default pe.conf
configuration values.

To restore the ability to inject defaults into generated pe.conf files,
revert this commit.

Remove hardcoded mem settings from default pe.conf