gitlab: Do away with generating tarball backups

Using GitLab's official backup tool takes too much time and, more importantly, space; /srv/gitlab is a bit over 430G but backing it up nearly exhausts its 1TB volume.

As we're creating btrfs snapshots and backing those up with borg, it seems unnecessary to also create tarballs of the same data. GitLab's documentation mentions snapshots as a viable backup strategy, and to the restored system it should seem like recovering from a power loss.

[1] https://docs.gitlab.com/ee/raketasks/backup_restore#alternative-backup-strategies

playbooks/tasks/include/upgrade-server.yml

@@ -27,14 +27,13 @@
 
 - name: check for active borg backup jobs
   block:
-    - name: get service facts
-      service_facts:
+    - name: check if /backup exists
+      stat: path=/backup
+      register: backup_mountdir
 
     - name: abort reboot when borg backup is running
       meta: end_host
-      when: >
-        ansible_facts.services["borg-backup.service"]["state"] == "running" or
-        ansible_facts.services["borg-backup-offsite.service"]["state"] == "running"
+      when: backup_mountdir.stat.exists
   when: "'borg_clients' in group_names"
 
 - name: gemini pre-reboot checks