Restore the package jobs
There are some uncertainties on how the new GitLab workflow should actually work for Apertis-native packages, so let's restore the package jobs for them.
We'll think about the best way to integrate them in the new world order later.
This affects the below repositories/packages:
- apertis/apertis-dev-tools
- apertis/apertis-eclipse-plugins
- apertis/chaiwala-bootflags
- apertis/chaiwala-user-session
- appfw/apertis-update-manager
- appfw/barkway
- appfw/beckfoot
- appfw/canterbury
- appfw/didcot
- appfw/frampton
- appfw/frome
- appfw/newport
- appfw/rhosydd
- appfw/ribchester
- appfw/traprain
- docs/apertis-designs
- docs/apertis-docs
- hmi/eye
- hmi/libclapton
- hmi/libgrassmoor
- hmi/liblightwood
- hmi/libseaton
- hmi/libshoreham
- hmi/libthornbury
- hmi/mildenhall
- hmi/mildenhall-compositor
- hmi/mildenhall-launcher
- hmi/mildenhall-popup-layer
- hmi/mildenhall-settings
- hmi/mildenhall-statusbar
- hmi/prestwood
- hmi/shapwick
- hmi/tinwell
- infrastructure/apertis-customizations
- infrastructure/apertis-tests
- tests/apertis-test-cases
- tests/apparmor-bluez-tester
- tests/apparmor-chaiwala-system-tester
- tests/apparmor-dbus-tester
- tests/apparmor-pulseaudio-tester
- tests/apparmor-tumbler-tester
- tests/bluez-phone-tester
- tests/cgroups-resource-control-tester
See https://phabricator.apertis.org/T6222 for more context.