management: Skip hourly crons during deploys.

This is most important for `send_zulip_update_announcements`, which
can race with the version run as a post-deploy hook.  However, all of
these crons can tolerate being slightly delayed, and there's little
benefit to them taking CPU or possibly hitting odd borderline race
conditions when the deploy is in progress.

For safety, we only trust the deploy lockfile if it was created
within the last hour -- deploys should not take more than an hour, and
failing to ever run hourly crons is much worse than perhaps running
them during a real very-long deploy.

analytics/management/commands/update_analytics_counts.py

@@ -10,7 +10,7 @@ from django.utils.timezone import now as timezone_now
 from typing_extensions import override
 
 from analytics.lib.counts import ALL_COUNT_STATS, logger, process_count_stat
-from zerver.lib.management import ZulipBaseCommand, abort_unless_locked
+from zerver.lib.management import ZulipBaseCommand, abort_cron_during_deploy, abort_unless_locked
 from zerver.lib.remote_server import send_server_data_to_push_bouncer, should_send_analytics_data
 from zerver.lib.timestamp import floor_to_hour
 from zerver.models import Realm
@@ -38,6 +38,7 @@ class Command(ZulipBaseCommand):
         )
 
     @override
+    @abort_cron_during_deploy
     @abort_unless_locked
     def handle(self, *args: Any, **options: Any) -> None:
         self.run_update_analytics_counts(options)