Rate limit docs had a issue due to the wrong request type by accident. This was not noticed due to both bots can work with rate limits. Synapse Admin links where also bugged but now fixed.

Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2905#issuecomment-1726892215

Update beeper-linkedin 0.5.4 -> latest (security fix)

Update mautrix-twitter 0.1.6 -> 0.1.7

Update mautrix-whatsapp 0.10.1 -> 0.10.2

Update mautrix-instagram 0.3.0 -> 0.3.1

Update mautrix-facebook 0.5.0 -> 0.5.1

Update telegram 0.14.1 -> 0.14.2

Update grafana 10.1.1 -> 10.1.2

Make borgmatic container tmp dir size configurable

Only available since v16.0-2 of the Postgres role.

Many of these do depend on the Synapse master process (`matrix-synapse.service`),
so it makes sense to do it.

Furthermore, we're doing it so that one can stop the `matrix-synapse.service`
service and have systemd cascade this into stopping all the workers as well.

This is useful for easily stopping all of Synapse, so that Postgres
upgrades (`--tags=upgrade-postgres`) can happen cleanly.
Postgres upgrades currently stop `devture_postgres_systemd_services_to_stop_for_maintenance_list` which
includes Synapse, but stopping just the master process and leaving workers running is not safe enough and sometimes leads to errors like:

> ERROR:  insert or update on table "event_forward_extremities" violates foreign key constraint "event_forward_extremities_event_id"

With this dependency in place, stopping `matrix-synapse.service` will stop all Synapse processes.

Update matrix-appservice-discord

Update synapse 1.92.1 -> 1.92.2 (security fix)

Update element 1.11.42 -> 1.11.43

Update Element 1.11.41 -> 1.11.42

Update jitsi v8922-0 -> v8922-1

Related to https://github.com/matrix-org/synapse/pull/16265

Update Draupnir from 1.85.0 to 1.85.1

Fix mautrix-gmessages branch