Add CI config using some of the common pipeline and a new build profile
We have been lacking CI for the linux package for about a decade, and generally have to rely on local builds or eyeballing to find problems with merge requests. This greatly increases the friction for working on the package.
With the current state of Salsa and its shared runners, comprehensive CI is not possible, but this gets us at least some of the way there:
- Fix terse builds (DEB_BUILD_OPTIONS=terse) to not be completely silent. Use this option to keep build logs within the limit.
- Introduce classes for build restrictions in debian/control.
- Implement a new build profile, pkg.linux.quick, that can be built within the time limit on the current shared runners.
- Use part of the common salsa-ci pipeline, but replace the extract-source and build jobs to avoid hitting a limit on the size of artifacts.
- Move Python static checks from autopkgtest to separate CI jobs.
- Add kconfig static check in CI.