Find a better heuristic for the packages which need to be released

Our repositories hold our own developed packages for which we maintain source code but also a set of dependencies that are different per repository, distro and version. When we do a release, our scripts need to update the version number in the RPM spec files and in the debian/changelog.

In the RPM file it is done by mean of a variable declared in the spec file that is only used in our own package, so there's no possibility of releasing a RPM which is not ours.

For the Debian package this is not the case and the heuristic currently used is the look if the current version is the same as the branch that we're closing and updating the release number only in that case. But this is safe is it is possible that one of the dependency that our repo holds has the exact same version number as our own. And updating that dependency version will brake the build because the orig tarball will not exist (which is correct). We should find a better way of looking at which debian/changelog files need to be updated after a release.

This is managed in the bin/common file.

Start in bin/common around line 151 and inspect how release scripts decide which debian/changelog files to update, comparing that logic with the RPM spec-file handling described in the issue. Define a safer way to distinguish repository-owned Debian packages from dependencies, then verify that dependency versions are not changed and the release build still uses the correct changelogs.