This is provoked by de91fe933d94afcdbfdb0c6cf75a1dfa43dfdf43,
where I've added a few new labels and made it possible for people to
disable them.

In this patch, I'm making it possible to disable any of the old Traefik
labels in a similar way.

Related to:

- https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3409
- https://github.com/t2bot/matrix-media-repo/releases/tag/v1.3.5
- https://github.com/matrix-org/matrix-spec-proposals/pull/3916

Support for authenticated media routes is enabled by default, but
variables are in place to disable it if necessary.

This change has not been tested.

Update ghcr.io/t2bot/matrix-media-repo Docker tag to v1.3.6

Update dependency prometheus to v2.53.1-0

My alerts seem to contain `annotations.alertname` in the payload, so the
default configuration (coming from the matrix-alertmanager-receiver README)
seems to be outdated or something.

Update awesometechnologies/synapse-admin Docker tag to v0.10.2

* Add public url for gitlab hookshot to autocreate webhook on gitlab instance

* Add `noqa var-naming` comment to variable

---------

Co-authored-by: Slavi Pantaleev <slavi@devture.com>

Update vectorim/element-web Docker tag to v1.11.70

Update dependency etherpad to v2.1.1-0

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

Update broken link in configuring-playbook-prometheus-grafana.md

* honoroit v0.9.22

* Add more spaces before comments to make yamllint happy

* Add more spaces before comment to make yamllint happy

---------

Co-authored-by: Slavi Pantaleev <slavi@devture.com>

HTTP/3 is no longer considered experimental in Traefik v3,
so it's a good time to enable it.

`matrix-media-repo` is the only role that seems incompatible with the
changes introduced by Traefik v3, due to its use of `PathPrefix` with
regular expressions in a few places.

Regular expressions should now be used with `PathRegexp`, not
`PathPrefix`. Furthermore, they should follow the Golang regexp syntax,
as described in the migration guide:
https://doc.traefik.io/traefik/migration/v2-to-v3-details/#dynamic-configuration-changes

Upgrade Jitsi (v9584-0 -> v9584-1)

This reverts commit 752de4406e.

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

When running the playbook against an existing server, it invokes `register_new_matrix_user`
as part of the `matrix-user-creator` role, which runs before the
`systemd_service_manager`. At that time, `matrix-user-creator` detects
that Synapse is up (from before), but it's the old version. Services have not yet been
restarted, so it's actually the older Synapse version that is up, not
the new one. The old version does not support the `--exists-ok` flag yet.

Basically, this `--exists-ok` patch landed too early and has affected existing playbook
users that have an older version of Synapse in operation.

It will be safer to bring back this patch some time in the future.
However, users upgrading from Synapse <= v1.109.0 even long into the
future will bump into the same issue. As such, it would be better to
either add special handling or to delay bringing back this patch enough
so as to ensure everyone using the playbook is on Synapse >= 1.110.0.

Related to https://github.com/element-hq/synapse/pull/17304

chore(deps): update ghcr.io/element-hq/synapse docker tag to v1.110.0

Upgrade Jitsi (v9457-5 -> v9584-0)

chore(deps): update ghcr.io/matrix-org/sliding-sync docker tag to v0.99.19

Allow configuring synapse `auto_join_mxid_localpart`