To fix the issue that currently prevents the second image (with the /lit
path prefix) to be built and pushed (both for releases and nightly
builds), we clear the build cache between builds.
Added a daily schedule to the Docker workflow to automate builds and
pushes of the `daily-testing` image. This change introduces a new cron
job that runs every day at midnight (UTC) and triggers the workflow.
We want to allow users to use LiT under a custom path to make it easier
to integrate LiT in bundled software such as BTCPayServer. Because the
custom path prefix must be known at build time, we create an additional
docker image that uses the static /lit path as the prefix.
To avoid leaking any sensitive information like Docker Hub credentials
because of compromised actions repositories, we use our own, vendored
actions for all steps that potentially touch sensitive information.
To disincentivize users of 32bit machines to use lnd, we removed the
ARMv7 (32bit) target for docker images there. It therefore doesn't make
sense to provide LiT images for 32bit machines either.
We add a GitHub workflow that is triggered whenever a new version tag is
pushed. It will trigger a docker image build for that version and
automatically push it to the specified repo.
