It requires files (in the packaging directory) that have since been
moved to their own repository. We could fetch the additional repo, but
as far as I know, no one is using the artifact from the job at this time.

1. Set ERLANG_VERSION explicitly in the rabbitmq_peer_discovery_aws
tests as terraform requires it (it should already be present in our ci
docker images, but I have not figured out why not yet)
2. Ensure that 'rabbit' & 'finish' jobs in actions do not run for
cancelled workflows

except rabbitmq_codegen

these images are used by the github actions workflows, and though
while not sensitive, are not intended to be published

This workflow will run on a schedule rather than on every push

Mix clusters with v3.7 and v3.8, currently on both erlang versions. As
this also increases the actions duration rabbit ct-* suites have been
de-grouped such that multiple ct suites are no longer run as part of a
GitHub Actions job.

Using a unique span_id when invoking the buildevents cli

Dialyze now runs independently for each component on the uncompiled sources
to maximize the amount of issues detectable

For Erlang/OTP 22 & 23

- Provide RABBITMQ_VERSION so that plugin version compatibility checks work
  correctly
- Run tests generally as an unpriveleged user in docker, like we do in concourse
- Set USER in the env for erlang-cookie-sources tests