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

.. when `matrix_nginx_proxy_enabled: false`

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

docs/configuring-playbook: Add link to etherpad configuration

Add ability to sync only direct Chats in TG-Bridge

update docs to exclude grou-sync

add option to change filter_mode

add default for TG filter_mode

These Postgres configuration variables are part of the `database.yaml` file
and don't need to be here.

This allows people to augment the Synapse image with custom tools and
addons without having to rebuild it from scratch.

If customizations are enabled, the playbook will build a new
`localhost/matrixdotorg/synapse:VERSION-customized` image
on top of the default one (`FROM matrixdotorg/synapse:VERSION`)
and with custom Dockerfile build steps.

For servers that self-build the Synapse image, the Synapse image will be
built first, before proceding to extend it the same way.

In the future, we'll also have easy to enable Dockerfile build steps
for modules that the playbook supports.