bullseye upgrades, second batch

upgrade the following servers to Debian bullseye:

• bacula-director-01 (@lavamind)
• bungei (@lavamind) psql 13 upgrade @anarcat
• carinatum @anarcat (triggered #40751 (closed))
• check-01 @anarcat left tpo/network-health/exitmap#38 (closed) also generated tpo/network-health/metrics/exit-scanner#40004 (closed), tpo/network-health/metrics/tor-check#40007 (closed)
• colchicifolium @lavamind
• crm-ext-01 @anarcat
• crm-int-01 @anarcat
• fallax @anarcat
• gayi (yes, it needs to be upgraded, see #17202 ) @anarcat
• gettor-01 - sync with @meskio, AFK on may 2nd, <= 1800UTC otherwise @anarcat no need, will be retired, see #40915 (closed)
• gitlab-02 @anarcat, planned for Monday, May 30 @ 17:00 UTC
• henryi @anarcat
• majus @lavamind
• mandos-01 @lavamind
• materculae @anarcat led to OOM issues? see #40750 (closed)
• meronense - do NOT upgrade PostgreSQL until we figure out issues with PostgreSQL 13 (#40750 (closed) and #40761 (closed) ) things seem to have resolved themselves @anarcat see #40809 (closed) for the Postgresql 13 upgrade
• neriniflorum @lavamind
• nevii @lavamind
• onionbalance-01 (retired)
• onionbalance-02 @lavamind
• onionoo-backend-01 @lavamind
• onionoo-backend-02 @lavamind
• onionoo-frontend-01 @lavamind
• onionoo-frontend-02 @lavamind
• polyanthum - sync with @meskio, AFK on may 2nd, <= 1800UTC otherwise, also deploy backports, see #40758 (closed) @anarcat possibly caused tpo/anti-censorship/bridgedb#40049 (closed)
• rude @lavamind
• staticiforme @anarcat
• subnotabile to retire? see #40810 (closed)