The `config:check-formatting` and `docs:check-formatting` tasks have no value to the developer, since they will be better
off to just run the formatting task. This means that the only use for this task is the CI. I think this can be better
achieved by configuring the CI to format the code and then check for a diff. This ensures that there is no possibility
for a mismatch between the formatting check and the formatting task.

The Prettier formatting tool supports a long list of languages. Previously, it was being arbitrarily limited to JSON,
YAML, and Markdown files. It will be more useful to allow it to format files of any language it supports.

...filter
The workflow should run whenever this file is modified.

...w recursive
`.prettierrc` is the Prettier formatting tool's configuration file. Prettier uses the configuration file closes to the
file being formatted, meaning a project can have multiple configuration files. The workflow should run whenever any
configuration file is edited.

The `workflow_dispatch` event allows triggering the workflow via the GitHub web interface. This makes it easy to trigger
an immediate workflow run after some relevant external change.
The `repository_dispatch` event allows triggering workflows via the GitHub API. This might be useful for triggering an
immediate check in multiple relevant repositories after an external change, or some automated process. Although we don't
have any specific need for this event at the moment, the event has no impact on the workflow, so there is no reason
against having it. It is the sort of thing that can end up being useful if it is already in consistently in place, but
not worth setting up on demand, since the effort to set it up is greater than the effort to trigger all the workflows
manually.

These are the naming conventions established in the standardized template workflow.

... trigger event reference
The workings of the `workflow_dispatch` and `repository_dispatch` events is not obvious from the name. For this reason,
a comment was added to explain their working. But this information is explained well enough in GitHub's documentation, so
the workflow will be less cluttered by simply providing a reference link interested parties can easily follow to get all
the information on the events used by the workflow.

...her YAML file extension
There are two file extensions in common use for YAML files: `.yaml` and `.yml`. Although this project uses `.yml`
exclusively for YAML files, this is a standardized workflow which might be applied to projects that have established the
use of the other extension. It will be most flexible if it supports both.

This is the template workflow filename, which is intended to serve as a unique identifier, and thus must be a bit more
verbose.

The badges provide a prominent indication of the repository's CI status at a glance. This may help to bring potential
issues to the attention of the maintainers.

Prettier formatting is now being applied to all supported files rather than only Markdown and YAML files as previously.
Some files were not compliant.