Current draupnir does not listen to its name. This config change fixes this bug. This bodge is able to be removed once this is fixed upstream.

main.yml is not included due to that its changed separately.

Update heisenbridge 1.14.1 -> 1.14.2

Related to 6a31fba346d9da434, 6a31fba346.

Related to https://github.com/Awesome-Technologies/synapse-admin/issues/322

Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2444

Switching from doing "post-start" loop hacks to running the container
in 3 steps: `create` + potentially connect to additional networks + `start`.
This way, the container would be connected to all its networks even at
the very beginning of its life.

Related to https://docs.docker.com/engine/deprecated/#separator--of---security-opt-flag-on-docker-run

Update Prometheus to v2.42.0 from v2.41.0

Docker images are released now so this change can now be pushed.

Fix python packages path in synapse container

Container image not published yet.

Reverts #2438

Update synapse 1.75.0 -> 1.76.0; default room version 9 -> 10

Update prometheus 2.41.0 -> 2.42.0

Update element 1.11.21 -> 1.11.22

Update jitsi stable-8218 -> stable-8252

Update element 1.11.20 -> 1.11.21

Update cinny 2.2.3 -> 2.2.4

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2427

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2427

This just enables the endpoint, which is somewhat helpful, but not
really enough to scrape them. Ideally, we'd be injecting these targets
into the Prometheus scrape config too.
For now, registering targets with Prometheus is very manual
(`matrix_prometheus_scraper_postgres_enabled`, `matrix_prometheus_scraper_hookshot_enabled`, ..).
This should be redone - e.g. a new `matrix_prometheus_scrape_config_jobs_auto` variable,
which is dynamically built in `group_vars/matrix_servers`.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2427

`metrics_enabled` should only expose the metrics locally, on the
container network, so that a local Prometheus can consume them.

Exposing them publicly should be done via a separate toggle (`metrics_proxying_enabled`).
This is how all other roles work, so this makes these mautrix roles consistent with the rest.

Mautrix metrics

mautrix-slack: add team name in channel name template

Update borgmatic 1.7.5 -> 1.7.6

Update mautrix-discord latest -> 0.1.0

Update maubot 0.3.1 -> 0.4.0