When using `runCommandLocal`, clients are required to download imagemagick
and the source files, even if the theme is already available from a binary
cache.
This is mainly documentation changes.
Also changed the default of `targets.grub.useImage` to a hard false,
as Plymouth doesn't use the wallpaper image any more.
This means that the OEM logo can be used to have a seamless boot process.
(Copy it in PNG format from /sys/firmware/acpi/bgrt/image)
The width of the progress bar will be adjusted to suit the width of the logo.
There is now a choice to either follow the main theme or keep a black
background.
systemd-boot enables the black background by default, as it always has a
black background itself, and keeping the same colour throughout the
whole boot process looks cleaner than applying our theme at the first
opportunity.
Making palette.json part of the system closure will protect it from
garbage collection, so future configurations can be evaluated without
having to generate the palette again. The generator is not kept, only the
palette which came from it, so this uses very little disk space.
As evaluations will no longer need the palette generator unless the
wallpaper was changed, I've removed the recommendation to add a binary
cache - the overhead of querying the cache for unrelated builds
outweighs the remaining benefits of it.
The workflow attempts to skip the deployment step when it is run on other
branches, however environment protection rules are checked before this, causing
a failure.
The automatically chosen color is now the default value under `stylix.palette`,
rather than `null`.
The colors from `stylix.palette` are collected to make the default value
of `stylix.base16Scheme`.
If `stylix.base16Scheme` is overridden to an external file, the colors
from that file will NOT be written back to `stylix.palette`. For that
reason, you must still only refer to `lib.stylix.colors` within modules.
