Mainly for testing but it avoids an unnecessary setup of
`dockerode`

`semantic-release` does not pass `context` between stages.
Each stage must be _pure_.

We can re-use `verifyConditions` to populate the `context`
with the `dockerode` data for use.

Catches errors before we publish tag/release

This patch does some whitespace formatting but allows the
rest of the commit in this repository to be bundled up into
a `semantic-release`

We want to make users aware about the skipped Daemon test
if it is not ran rather than removing it from the testing
suite

`semantic-release` has a interesting plugin resolution logic.

If we name our plugin `index.js` it will resolve it down to
`node_modules/semantic-release/lib/plugins/index.js` which
is _not_ what we want.

Simple fix is to use the `plugin` nomenclature for our plugin

This will be in the next release of the templates

No need to add `esm` (which is unmaintained), we can just
use NodeJS dynamic import on the necessary `semantic-release`
plugin functions.

Need to load the CommonJS module

`semantic-release` requires this

Not available on NodeJS 14

We need support for multiple NodeJS caches to enable more versions.

We will start with NodeJS 14 because that is the minimum that
`semantic-release` supports.

Allows us to run the Docker Daemon test

The mock backend will not receive any backend hits.

It might take a long while to pull the image.

The Daemon does not seem to return an `IdentityToken`, we can
just pass the same authentication object to the pull/push

Can be enabled locally by providing:

- `CI_REGISTRY_IMAGE`
- `CI_COMMIT_SHA`
- `DOCKER_HOST`

It is likely that the auth variables will also be needed:

- `DOCKERODE_USERNAME`
- `DOCKERODE_PASSWORD`
- `DOCKERODE_SERVER`

Explain how to configure the plugin via configuration variables
and/or environment variables