bookworm upgrades, second batch

upgrade all those servers to Debian bookworm

• bacula-director-01.torproject.org (@lavamind)
• btcpayserver-02.torproject.org (@anarcat)
• bungei.torproject.org (@lavamind, crypttab had a typo, had to boot rescue to recover, grub KVM console seems inaccessible)
• carinatum.torproject.org (@kez, had issues during upgrade, followup in tpo/network-health/doctor#40034 (closed))
• check-01.torproject.org (@kez, had a prolonged outage: tpo/network-health/metrics/tor-check#40017 (closed), mod_qos broken, followup in #41509 (closed))
• colchicifolium.torproject.org (@anarcat)
• collector-02.torproject.org (@anarcat)
• crm-ext-01.torproject.org (@anarcat, PHP 8 compatibility issue, followup in #41511 (closed))
• crm-int-01.torproject.org (@anarcat)
• dangerzone-01.torproject.org (@kez)
• donate-review-01.torproject.org (@kez)
• gayi.torproject.org (@anarcat)
• gitlab-02.torproject.org (@anarcat, migrated to standalone postgresql following upgrade issue #41426 (closed))
• henryi.torproject.org (@kez)
• majus.torproject.org (@anarcat, obsolete transifex-client package left around)
• materculae.torproject.org (@lavamind, noticed extra load on the server, filed #41507 (closed))
• meronense.torproject.org (@lavamind, possible OOM regression see #41515 (closed))
• metrics-store-01.torproject.org (@anarcat)
• nevii.torproject.org (@anarcat, handful of issues with paths moved from /usr/sbin to /usr/bin)
• onionbalance-02.torproject.org (@anarcat)
• onionoo-backend-01.torproject.org (@anarcat)
• onionoo-backend-02.torproject.org (@anarcat)
• onionoo-frontend-01.torproject.org (@anarcat)
• onionoo-frontend-02.torproject.org (@anarcat)
• polyanthum.torproject.org (@lavamind)
• probetelemetry-01.torproject.org (@anarcat)
• rdsys-frontend-01.torproject.org (@anarcat)
• rude.torproject.org (@lavamind)
• survey-01.torproject.org (@lavamind)
• telegram-bot-01.torproject.org (@anarcat)
• weather-01.torproject.org (@anarcat, catastrophic data loss, see #41388 (closed))

31 machines

like the first batch, due date is approximate here, used to ping the team to organise this before the actual week planned in TPA-RFC-57, which is "last week of october".

an announcement need to be sent to remind people of this upcoming batch when the first due date is hit.