The publish step uploads one apk at a time, in glob order, and stops at
the first failed upload. With the kernel apk before soc-fairphone-fp6-audio
in that order, a failure in between would leave the registry serving a
kernel without the package that carries its card name's topology and UCM
(the combined-stable tip CI builds names the card MILOS-Fairphone-Gen6
since 7.3; only soc-fairphone-fp6-audio >= 5 has those files, and without
them that kernel boots with no sound card). Upload everything else first,
the kernel last.