Deploy visit-stats journal client on production

• Stop the loaders (so they won't fail and consume too much messages once the storage is stopped)
• Stop the storage service
• Upgrade the storage storage server to last version of swh-storage/swh-model/swh-journal
• Upgrade the storage database model
• Start the storage service
• Upgrade the replica db model so replication continues
• Upgrade and start the loaders
• Upgrade scheduler stack to last versions created during the sprint
• Stop swh-scheduler-runner to avoid blocking queries
• Upgrade the scheduler database model
• Restart scheduler service (gunicorn-swh-scheduler, swh-scheduler-runner, ...)
• Create consumer group swh.scheduler.journal_client so it starts at the end of the topics
• Deploy a new scheduler journal-client service on saatchi (which must start at the end of the topic)
• Launch a backfill of the origin_visit_status topic

---

Migrated from T2993 (view on Phabricator)