fix: use full paths

- remove doi_mint_pending_releases from backup
- doi_mint_pending_releases and doi_sync_all_metadata could be moved to
  /etc/cron.weekly or removed entirely since they are simply a fallback
  if the scheduled async huey doi sync fails

Author: alee

django/deploy/cron.daily/backup

@@ -4,12 +4,3 @@
 
 export DJANGO_SETTINGS_MODULE="core.settings.production"
 inv -r /code db.backup borg.backup >> /shared/logs/comses-backup.log 2>&1
-
-# FIXME: should we synchronize DOI metadata after backups or before backups?
-# Pros of after backups: DOI metadata syncing alters the DB and taking a snapshot backup before running this may protect against
-# errors or bugs that happened as a result of the sync
-#
-# Pros of before backups: backups will be more up-to-date
-#
-# currently syncing after backups
-./manage.py doi_mint_pending_releases --no-interactive --no-dry-run

django/deploy/cron.daily/doi_mint_pending_releases

@@ -7,4 +7,4 @@
 # Pros of before backups: backups will be more up-to-date
 #
 # currently syncing after backups
-./manage.py doi_mint_pending_releases --no-interactive --no-dry-run
+/code/manage.py doi_mint_pending_releases --no-interactive --no-dry-run

django/deploy/cron.daily/doi_sync_all_metadata

@@ -1,3 +1,3 @@
 #!/bin/sh
 
-./manage.py doi_sync_metadata --no-interactive --no-dry-run
+/code/manage.py doi_sync_metadata --no-interactive --no-dry-run