Drop packaging jobs that already converted to GitLab-to-OBS machinery

Packages for which Apertis is the upstream used to not native, we used to build these in these jenkins job with a pre-generated original tarball.

And these Jenkins job can lead to nasty results when targeting multiple releases at the same time: with the new release flow this is now much more common and it is a growing source of errors that can be solved by moving to the GitLab-to-OBS pipeline, since it already deals with the issue properly

To simply the workflow. We have converted these Apertis-specific "upstream" packages from jenkins jobs to the GitLab-to-OBS machinery.

Apertis Developers now only have to deal with one single GitLab-CI workflow for these Apertis-sepcific "upstream" packages.

This step toward moving away from Jenkins, to simplify our infrastructure and make it easier to be reproduced by downstreams Product team will be able to push their projects directly from GitLab to OBS with a much simpler workflow, requiring less support from the distribution maintainers.

Signed-off-by: Andrew Lee (李健秋) andrew.lee@collabora.co.uk