Rationale: the /.well-known/matrix/client should return only 200 as well, but it has hardcoded "safe" value, regardless the spec: https://spec.matrix.org/v1.4/client-server-api/#well-known-uri

So, why not do the same for the /.well-known/matrix/server?

update buscarron 1.2.1 -> 1.3.0

update postmoogle 0.9.7 -> 0.9.8

update honoroit 0.9.15 -> 0.9.16

update element v1.11.10 -> v1.11.11

Update grafana 9.2.1 -> 9.2.2

Update appservice-irc 0.35.1 -> 0.36.0

Fix 502

ref: 57bb340343

update Docs regarding Filter-Mode-Flag

Add information on how to manually run the backup

Signed-off-by: Julian-Samuel Gebühr <julian-samuel@gebuehr.net>

We're starting it with `--user` and dropped capabilities, after all.

Hopefully fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2188

update remote-repo-infos with link to doc

update link to example

in my environment i see the matrix. conf in that file: /matrix/nginx-proxy/conf.d/matrix-domain.conf

was a litte confusing for me, so i added the link to the syntax-descr.

We haven't encountered such a problem yet, but it doesn't hurt to
make things more robust.

These values that we were setting also make sense in the context of the
`matrix-postgres` role even when not used within the playbook.

grammar correction

the word "both" would refer to only 2 urls in this context

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

Just specifying `15` means we won't automatically re-pull `15.1` when it comes out.

We're overriding these in the correct way in `group_vars/matrix_servers`
so this wasn't causing any problem in practice.

Closes https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2180

add if hostname is not availble for SRV record

Update grafana 9.2.0 -> 9.2.1

Update Synapse 1.68.0 -> 1.69.0