ci: Use a more generic message for the automated commit

The automated commit may not just bump the version, but may update other
aspects of the base files, for instance:

1. applying changes to the customizations like adding new fields
2. downstream customizations changing the vendor metadata while the
   release codename remains the same

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

debian/apertis/local-gitlab-ci.yml

@@ -23,7 +23,7 @@ verify-release:
                     debian/apertis/update-base-files $release
                     if ! git diff --exit-code && test "${CI_COMMIT_BRANCH%%/*}" = "$OSNAME"
                     then
-                        git commit -a --author "$GITLAB_USER_NAME <$GITLAB_USER_EMAIL>" -m "Bump version numbers to $release"
+                        git commit -a --author "$GITLAB_USER_NAME <$GITLAB_USER_EMAIL>" -m "Update base files for $OSNAME/$release"
                         git push ${CI_AUTH_PROJECT_URL} HEAD:refs/heads/proposed-updates/$OSNAME/$release/version-bump -o merge_request.create -o merge_request.remove_source_branch -o merge_request.target="$OSNAME"/$release -o merge_request.title="Bump version numbers to $release"
                     fi
                 fi

debian/apertis/update-base-files

@@ -39,6 +39,6 @@ case "$pkg_ver" in
         ;;
 esac
 
-dch $dch_arg -D apertis --force-distribution "Bump version numbers to $version."
+dch $dch_arg -D apertis --force-distribution "Update base files for apertis/$version"
 
 dpkg-buildpackage -S -d --no-pre-clean -uc -us