Changes

osmo-gsm-tester: use debian's soapysdr-module-lms7

After switching from build.opensuse.org to obs.osmocom.org's published
packages, the soapysdr0.7-module-lms7 binary package we had does not
exist anymore.

I'm not sure where it came from, from the name it looks like it was
built from version 0.7 sources, but we only have a soapysdr_0.5.4
package in OBS that was added for debian 8/ubuntu 16.04 compatibility 4
years ago, and builds have been disabled for all architectures:
https://build.opensuse.org/package/show/network:osmocom:nightly/soapysdr

Instead of relying on this leftover binary package, use the one provided
by debian instead. This osmo-gsm-tester docker container is based on
debian-buster, which has soapysdr 0.6 packaged. If we should really need
0.7, we could switch it to bullseye or build it from source while
building the container, or add it back to obs.osmocom.org.

I verified that the container builds with this change.

Fix for:
  E: Unable to locate package soapysdr0.7-module-lms7

Change-Id: Ie2408258eda407d9db6c2f0f5fbe475861756778

release-tarball-build-dist: upgrade from debian 9

Let it use debian bullseye and rename the directory once, so we don't
need to rename it in the future when switching the debian version
again.

The reason I'm doing this now is that building with debian 9 failed
due to obs.osmocom.org related changes. It would be trivial to fix that,
but I decided to rather upgrade to the latest debian version.

Change-Id: Ib6039724a7200abce5252f95407047296b72cd51

release-tarball-build-dist: move osmo-ci code here

Add a jenkins.sh that does the same as the previous lengthy shell
command in the jenkins-job-builder file, and add
osmocom-release-tarballs.sh. This makes it easier to test the
script, and only patching one repository is needed from now on when
changing to a newer debian version.

Depends: osmo-ci I15f6c08b807f1462f91e95b624cdc1aad0592dd6
Change-Id: I4cf66097f508c029f688ec8af1cab2238d42f84f